OVMesh FAQ

• Region: United States
• Modem preset: Long Range Fast
• Channel 0: public LongFast
• Channel 0 key: AQ==
• Channel role: Primary
• Frequency slot: 0 (default)
• Maximum hops: 5
• Transmit enabled and OK to MQTT: Enabled
• Uplink and downlink: Enabled on every configured channel

The complete walkthrough is on the Device Setup page.

No license is required for normal OVMesh operation using the United States LoRa region and legal unlicensed-band settings. Amateur-radio mode has different privileges and restrictions: licensed operators must identify and may not use encrypted amateur transmissions.

Keeping public LongFast as the Primary channel lets a newly configured node communicate with the regional public mesh immediately. Its key, AQ==, is publicly known. It provides compatibility, not privacy.

Yes. Leave public LongFast unchanged as Channel 0 Primary, then add a private channel as Secondary with a unique name and a randomly generated key. Every trusted device needs the same secondary-channel name and key.

Slot 0 tells the firmware to derive the operating slot from the Primary channel name. Because OVMesh uses public LongFast as Primary, leaving the slot at zero preserves compatibility. Do not manually force slot 20.

Send a short test message on public Channel 0. Check whether a nearby node acknowledges or receives it, then move outdoors or to a higher location if necessary. If you add a private secondary channel, test it separately on devices that share its key.

Confirm the United States region, Long Range Fast preset, frequency slot 0, and matching public channel name and key. Check the antenna connection and move away from interior walls or metal. Node information is periodic, so discovery may take time. A node can also be out of range, muted, hidden, powered down, or listed under stale cached information.

Meshtastic is an open-source, decentralized messaging system for small LoRa radios. It supports short text messages, direct messages, position information, telemetry and other low-bandwidth data without requiring cell service, Wi-Fi or an internet connection.

Range depends far more on terrain, antenna height, antenna quality, obstructions and receiver noise than on a single mileage number. A clear elevated path can cover many miles; dense buildings, valleys and indoor placement can shorten it dramatically.

Meshtastic firmware permits up to seven hops, but OVMesh uses a hop limit of five. More hops are not automatically better: every additional relay consumes airtime and can increase congestion.

A normal Client participates in managed rebroadcasting when appropriate. Client Mute does not forward other nodes’ packets. Dedicated infrastructure roles behave differently and should be selected deliberately.

• Client: the right choice for most handheld and general-purpose nodes.
• Client Base: a stronger personal attic or roof node that prioritizes packets involving your favorited nodes.
• Client Mute: participates without relaying other nodes’ traffic.
• Tracker or Sensor: specialized roles for location or telemetry devices.
• Router or Router Late: planned infrastructure only. Contact OVMesh before deployment.

The old Repeater role is deprecated in current Meshtastic firmware.

No. Acknowledgements can show that another node heard a broadcast or that the intended direct-message recipient responded, but radio congestion, terrain, interference, sleeping hardware and changing paths can still cause failures. Meshtastic is not a replacement for 911 or other safety-of-life systems.

Apps retain a local node database. Use the Last Heard time to judge whether an entry is current. Old entries can remain after a node moves, changes identity or goes offline.

Channels are logical message groups that share the same LoRa radio settings. Devices need compatible region and modem settings, plus a matching channel name and key, to exchange messages on that channel. Periodic position and telemetry broadcasts normally use the Primary channel.

Meshtastic encrypts channel payloads, but encryption is not the same as privacy. The public AQ== key is known to everyone. Use a random 256-bit key on a private secondary channel for private group traffic. Packet headers remain visible so nodes can relay packets they cannot decrypt.

Current firmware uses public-key cryptography for direct messages after the devices have exchanged keys. Keep firmware current and verify the intended recipient before sharing sensitive information. Meshtastic should not be treated as equivalent to a modern high-security messaging service.

Yes. The default rebroadcast behavior can forward packets from compatible meshes even when the relay does not have the channel key. This is an important part of how separate private groups can benefit from shared radio infrastructure.

Meshtastic apps can generate a QR code or URL containing channel and LoRa settings. Treat it like a credential: review the settings and only import codes from trusted sources because scanning one can change more than a channel name.

Position precision is configured per channel. Set public-channel precision conservatively or disable position sharing if exact location is unnecessary. MQTT map reporting is separate and may publish a node’s name, approximate position, hardware, role and firmware information.

MQTT is an optional internet gateway. A gateway node can publish radio packets to a broker and bring broker packets back onto the local mesh. The radio mesh itself does not require MQTT or internet access.

• OK to MQTT records your consent for eligible public-key packets to be uplinked by official firmware.
• Uplink permits a channel’s mesh packets to be published by a configured gateway.
• Downlink permits MQTT packets for that channel to enter the radio mesh.

These are separate controls. OVMesh currently recommends enabling all three for the regional configuration.

Yes, depending on configuration. MQTT can carry encrypted or unencrypted packets; JSON output is unencrypted, and map reports intentionally publish node information. TLS only protects the connection to the broker. Review every MQTT privacy option before using custom brokers, bots or dashboards.

Choose a device supported by current Meshtastic firmware and suitable for its job. OVMesh generally recommends RAK Wireless nRF52-based hardware for excellent battery life, modular sensor options and reliable solar or fixed installations. Screen-equipped ESP32 devices can be convenient for experimentation but usually consume more power.

Prices change, but many handheld builds fall roughly between $50 and $120. Weatherproof fixed or solar installations often cost $100 to $200 or more after the antenna, enclosure, battery, panel, mounting hardware, grounding and cable are included. Meshtastic itself has no required subscription.

Improve antenna placement before increasing complexity. Height, a clear path, low-loss coax, a properly tuned antenna and distance from noisy electronics usually matter most. Avoid long runs of thin coax. A single well-placed node can outperform several poorly placed nodes.

Use stable power, weather protection and the best practical antenna location. Client is suitable for most nodes. Client Base is useful when a strong attic or roof node should favor traffic involving your weaker personal nodes; mark those nodes as favorites on the base.

Only after network planning. Router and Router Late are infrastructure roles, not upgrades for an ordinary rooftop. Poorly placed prioritized routers can consume hops and airtime. Contact OVMesh so the site, coverage objective and surrounding network can be evaluated first.

• Attach the correct antenna before powering or transmitting.
• Verify battery polarity before connecting a battery.
• Use weatherproof cable entries and strain relief outdoors.
• Plan grounding, surge protection and lightning protection for elevated antennas.
• Keep antennas and structures clear of power lines.

Use conservative reporting intervals. Temperature, humidity, pressure, air quality, battery and power telemetry can be useful, but frequent broadcasts consume shared airtime. Match the interval to how quickly the measurement actually changes.

Use the official Meshtastic Web Flasher and choose a current stable or recommended release for your hardware. Save channel keys and important configuration before a full erase.

Some supported devices have a screen, keyboard or buttons for standalone messaging. Other nodes connect to Android, Apple or web clients over Bluetooth, USB, Wi-Fi or Ethernet depending on their hardware.

Start with the OVMesh community and include the device model, firmware version, role, region, modem preset, channel setup, power source and a clear description of the problem. Do not post private channel keys, passwords or precise private locations.