Node Configuration

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

Firmware

Flash from the Meshtastic web flasher over USB, using Chrome or Edge. The flashing documentation covers ESP32 and nRF52/RP2040/RP2350 boards separately; the procedure differs by family. Install the serial drivers first if the board is not detected.

Channels

Alongside the primary channel, Florida uses:

Open a channel name on a device with the app installed to add it, or enter the name and key by hand as a secondary channel. Name and key together define the channel: same name, same key, same channel. Names are case sensitive and limited to 11 characters. A node has eight channel slots including the primary.

The Weekly Mesh Net runs on your region’s default public channel, not on any of these. Bot traffic goes on testing or a private channel; keep emergency clear. See Bots and Automation.

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:

Radio Configuration

Channels:

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

Uplink and downlink are per channel:

FloridaMesh and emergency take downlink so traffic on them reaches the whole state instead of only nodes in radio range of the sender.

The Florida broker zeroes hop_limit and hop_start in flight on the default modem-preset channels and on telemetry. Packets it delivers on those reach only nodes hearing a gateway directly and are not rebroadcast, so MQTT traffic cannot flood the radio mesh. FloridaMesh and emergency are not zero-hopped; downlinked traffic on them propagates at its hop limit.

Device:

• Role: CLIENT|CLIENT_BASE|CLIENT_MUTE³

LoRa:

• Presets: LONG_FAST⁴
• Hop limit: 3⁵
• Ignore MQTT: Unchecked⁶
• OK to MQTT: Checked⁷

Module Configuration

MQTT:

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

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

Neighbor Info:

• Neighbor Info enabled: Checked¹⁰
• 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

FAQ

My 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

I receive too many notifications on a channel

Notification behaviour is local to your phone. Messages keep arriving either way, and your node keeps relaying traffic for the mesh.

• Mute the conversation. Select the channel in the message list, then Mute notifications: 8 hours, 1 week, or always.
• Disable notifications for the app in your phone’s settings.
• Remove the channel in the app’s channel settings, freeing the slot. Rejoin later with the name and key above.