Set up your mesh node

Important Hardware Warnings (Read First)

If you are assembling your device yourself:

Check battery polarity before connecting anything

You absolutely must verify battery polarity. Batteries and connectors are not standardized across every device and vendor, and polarity can vary. If you connect the battery backwards, you can instantly fry the board. Vendors generally will not refund or warranty damage caused by reversed polarity.

Never power a radio without an antenna attached

Do not apply power to the device unless the antenna(s) are attached. Transmitting without an antenna can damage the radio hardware. Vendors generally will not honor warranty claims for damage caused by powering or transmitting without an antenna connected.

Flash the Firmware First

What you need

• A data-capable USB cable (many charge-only cables will not work)
• A computer with Google Chrome or Microsoft Edge
• Your Meshtastic device

Flash using the Meshtastic Web Flasher

1. Open Chrome or Edge.
2. Go to flasher.meshtastic.org.
3. Plug your device into your computer using a data-capable USB cable.
4. In the flasher, select your device type from the list.
5. Select the current stable firmware option shown by the flasher.
6. If the flasher offers a full erase or factory erase option, use it for a clean start.
7. Click Flash and follow the prompts to select the correct USB device when your browser asks.

If the flasher cannot connect, put the device into flashing mode

Some devices require a bootloader or programming mode. Try these common methods:

• Hold the BOOT or PRG button while plugging in USB, then release once detected.
• Double-press RESET to enter bootloader mode (common on some boards).

Then retry the flash process.

Windows USB Driver Instructions (Only If Needed)

If Windows does not detect your device properly, or the flasher cannot connect, you may need a USB-to-serial driver (most common with ESP32-based devices).

1. Plug in the device.
2. Open Windows Device Manager and look for:
   • A new COM port, or
   • An unknown USB device
3. Identify the USB serial chip used by your device (common: CP210x or CH9102/CH34x families).
4. Install the matching Windows driver using the official links provided in the Meshtastic documentation.
5. Unplug and replug the device.
6. Confirm a COM port appears in Device Manager.
7. Retry the Meshtastic Web Flasher.

Connect to Your Node After Flashing

After flashing, connect using one of these methods:

• Phone app via Bluetooth (most common)
• Phone app via Wi-Fi (sometimes used for base nodes)
• Meshtastic Web Client (useful on desktop)

Apply OV Mesh Baseline Settings (United States Only)

Do these steps in the Meshtastic app or web client.

Radio and LoRa settings

Set these first:

• Region: United States
• Use preset: Enabled
• Preset: Long Range Fast
• Transmit enabled: Enabled
• OK to MQTT: Enabled
• Frequency slot: 0 (default)
• Max hops: 5

Device role

Use only these device roles unless you have a legitimate a special case. OVmesh can help you make that determination.

Choose one:

• Client
  Use for most handheld and everyday nodes.
• Client Base
  Use for a fixed, always-on home or business node with good placement.
• Client Mute
  Use for a quiet monitoring node or troubleshooting when you do not want your device contributing extra traffic.

Optional roles only when they match your purpose:

• Tracker
  Use only if the node’s main purpose is location reporting (hiking, vehicles, events). Keep location sharing intentional and avoid overly frequent updates.
• Sensor
  Use only if the node’s main purpose is telemetry (temperature, voltage, or other sensors). Keep telemetry intervals conservative so you do not spam the mesh.

Do not use:

• Router
• Router-Late
• Repeater (deprecated)
• Any other routing-boosting modes

These modes are for rare tower-level deployments. Used incorrectly, they can increase airtime, increase collisions, and make the mesh worse for everyone.

Bluetooth security

Do this immediately:

• Set a fixed Bluetooth PIN or password.
• Do not leave the default or insecure pairing behavior enabled.

This prevents random nearby devices from pairing to your node and changing your configuration.

Channel setup: public primary

Channel 0 is the shared public LongFast channel. Keeping the public channel primary makes a new node immediately interoperable with the regional mesh.

Channel 0 (Primary, public)

• Name: LongFast
• Key: AQ==
• Channel role: Primary
• Uplink enabled: Enabled
• Downlink enabled: Enabled

Optional private channels (Secondary)

• Add a private channel only as a Secondary channel; keep Channel 0 unchanged.
• Choose a unique channel name and generate a private 256-bit key.
• Use the same name and key on every trusted device that needs access.
• Enable both uplink and downlink for every configured channel.

MQTT permissions: In the LoRa settings, enable OK to MQTT. In each channel’s settings, enable both Uplink and Downlink, including the public primary channel and any private secondary channels.

Keep the public defaults: Do not replace the LongFast key AQ==, and leave the frequency slot at its default value of 0.

Display settings

• Units: Imperial

Private Channel Key Guidance (Optional)

The public primary LongFast key (AQ==) is intentionally shared and should remain unchanged. Rotate only the key for an optional private secondary channel if:

• A device is lost or stolen
• A device is sold or given away
• Someone who had access should no longer have access
• You accidentally shared the private key

After rotating a private secondary-channel key, update that same channel on every trusted device that needs access.

Final Sanity Checks

Before you call it done:

1. Confirm Region is set to United States.
2. Confirm preset is Long Range Fast.
3. Confirm frequency slot is 0 (default).
4. Confirm OK to MQTT is enabled.
5. Confirm max hops is 5.
6. Confirm your device role is Client or Client Base (or Client Mute if you intentionally want it quiet).
7. Confirm Bluetooth has a fixed password.
8. Confirm Channel 0 is LongFast with key AQ== and role Primary.
9. Confirm every configured channel has both uplink and downlink enabled.
10. Send a test message on Channel 0 to confirm you can talk to nearby nodes.
11. If you configured an optional private secondary channel, send a test message there to confirm all authorized devices share the same private key.

That’s it. Your node is now flashed, secured, and configured to work properly with the Ohio Valley Mesh.