Browse Docs

Node Configuration

Beanfield Json_18 PockyBum522 Jeremy (KQ4AFY) Bouse January 19, 2026 5 min read Guide

Recommendations for configuring your node and contributing to the mesh.

On this page

Below are configuration recommendations for optimizing your Meshtastic nodes for getting on the Florida Mesh Map & Florida Mesh Telemetry.

Getting on the Map In Existing Meshes

For nodes that are in established meshes (please check Florida Mesh Map to see where the closest feeders are) all you need to get added to the maps and tools is one config change.

LoRa:

  • Ok to MQTT: Checked

This change will allow for MQTT feeder nodes in the area that can hear you via RF to have permission to go and uplink your node’s info to the MQTT Map and Telemetry toolset. If you would like to help feed the map yourself, or are in an area with limited feeders. Please continue on.

Setting up a MQTT Gateway

If you would like to connect your nodes to the MQTT broker and provide telemetry to both the Florida Mesh Map & Florida Mesh Telemetry, you will need to configure the following settings:

Note

The Florida Mesh MQTT Server Primary purpose has been to provide data to help build and grow the Mesh across the state of Florida; hence this server from the start only allowed Uplinking (meaning comunication via this mqtt would not work). The data has been available to be viewed on both the Florida Mesh Map & Florida Mesh Telemetry.

Due to demand of users and need to be able to quickly identify and address issues, the Florida Mesh MQTT Server has moved to individual MQTT accounts rather than a singular shared credential. This now means you will need to use @MeshBot on the Discord server to request your account in order to connect to the Florida Mesh MQTT Server.

Radio Configuration

Channels:

  • LongFast (primary)
    • Uplink Enabled: Checked
    • Downlink Enabled: Unchecked1
    • Position enabled: Checked
    • Precise Location: user preference
    • Precision Slider: user preference

Device:

  • Role: CLIENT|CLIENT_BASE|CLIENT_MUTE2

LoRa:

  • Presets: LONG_FAST3
  • Hop limit: 34
  • Ignore MQTT: Unchecked5
  • OK to MQTT: Checked6

Module Configuration

MQTT:

  • Enabled: Checked
  • MQTT Server Address: mqtt.areyoumeshingwith.us
  • MQTT Username: your MQTT account credentials7
  • MQTT Password: your MQTT account credentials7
  • Encryption Enabled: Checked
  • JSON Enabled: Unchecked
  • TLS Enabled: user preference8
  • Root topic: msh/US/FL

Tip

If you followed the above MQTT steps in order, then you need to hit “Send” to update the device at this point before you proceed to the below four steps. Otherwise the send button will be grayed out.

  • Map reporting: Checked
  • Map reporting interval (seconds): 10800
  • Precise location: user preference
  • Precision Slider: user preference

Neighbor Info:

  • Neighbor Info enabled: Checked9
  • Update interval (seconds): 14400
  • Transmit over LoRa: Unchecked

Special Settings for Mobile Nodes and NRF52 Nodes

If your wanting to run a MQTT feeder from a mobile NRF52 or ESP32 based node. You’ll need to enable an additional setting.

MQTT:

  • Proxy to Client: Enabled

This will let the node pass MQTT data via the phone to the MQTT server.

If your using a NRF52 based node for a Base Station for example its best practice to use a secondary node that can either run off WIFI or ethernet, like a ESP32 based node or Portduino (Linux) based node, to operate as the feeder node. If you do run secondary feeder node, remember to set it to Client_Mute to prevent it from causing unnecessary noise. You can feed directly from a NRF52 via a phone but longterm its not the most reliable, since the connection is done over Bluetooth. Its best for adhoc quick deployments and mobile use.

Verifying Your Configuration

After configuring your device, you can verify that your telemetry is being properly reported:

  1. Check the Florida Mesh Map & Florida Mesh Telemetry - your node should appear within 15-30 minutes, check for the hardware MAC ID first, since this will be the first part to populate
  2. Review your device debug logs for successful MQTT connection messages
  3. Confirm your device is sending position updates at the expected intervals

Troubleshooting

If your node is not appearing on the map:

  • Verify internet connectivity on the device
  • If its a NRF52 based node confirm that Proxy to Client is enabled.
  • Check that your MQTT credentials are entered correctly
  • Ensure the precision settings meet the minimum requirements (1194ft / 363m)
  • Confirm the root topic is set exactly to msh/US/FL
  • Verify the MQTT module is enabled and properly configured

  1. If you wish to receive traffic from MQTT and not just send traffic to MQTT then you may enable with your individual MQTT account credentials. ↩︎

  2. CLIENT, CLIENT_BASE, or CLIENT_MUTE unless you have a different use case. Never set this to ROUTER or REPEATER. ↩︎

  3. Please reference Regional LoRa Settings for up to date modem presets for each area of the state. ↩︎

  4. Except in specific use cases (user preference: but do not set to higher than 5). ↩︎

  5. Can be Checked to stop rouge MQTT data from appearing on your node and hopping though. Consider unchecking if you uncheck downlink. ↩︎

  6. This gives permission to uplink your node to MQTT Servers. You will not appear on the Meshtastic Map if this is not enabled. ↩︎

  7. Florida Mesh has a new requirement to request an individual MQTT account which allow both channel uplink & downlink ability. ↩︎ ↩︎

  8. TLS encrypts data transmitted between MQTT clients and the broker for increased security, but may not supported on all platforms. It is known that the Android App version above 2.7.13 may have issues with TLS enabled. ↩︎

  9. Please only enable Neighbor Info on Basestation and stationary nodes, when enabled on mobile nodes it causes a lot of noise and clutter to the map. Thank you. ↩︎

Regional LoRa Settings
Meshtasticd Installation, ESP32 remote Firmware Updating