Getting Started

• 1: Meshtastic Basics
• 2: MQTT
• 3: Recommended Hardware
• 4: Recommended Settings

1 - Meshtastic Basics

Introduction to Meshtastic

Meshtastic is an open-source project that enables long-range, low-power, mesh communication using inexpensive hardware. It is primarily designed for outdoor activities, emergency scenarios, and other use cases where traditional communication infrastructure is unavailable.

Core Components

1. Hardware

   • LoRa Modules: Meshtastic uses LoRa (Long Range) modules, which are capable of transmitting data over several kilometers using minimal power. Commonly used modules include the TTGO T-Beam and Heltec WiFi LoRa 32.
   • Microcontrollers: These modules are typically integrated with microcontrollers that handle data processing and communication.

2. Firmware

   • The Meshtastic firmware is installed on the LoRa modules, enabling them to form a mesh network. This firmware manages the routing of messages, device configurations, and network management.

3. Mobile Applications

   • Meshtastic App: Available for both Android and iOS, the Meshtastic app allows users to configure their devices, send messages, and visualize the mesh network. It connects to the LoRa modules via Bluetooth.
   • Web Interface: There is also a web interface that provides similar functionalities through a web browser.

How Meshtastic Works

1. Mesh Network Formation

   • Node Deployment: Each LoRa module acts as a node in the network. When powered on, these nodes automatically connect to nearby nodes, forming a mesh network.
   • Self-Healing and Scalability: The network is self-healing, meaning it can dynamically re-route messages if a node goes offline. This makes the network robust and scalable, capable of handling numerous nodes.

2. Communication

   • Message Routing: When a message is sent from one node, it is propagated through the mesh network. Nodes relay the message until it reaches its destination.
   • Encryption: Messages are encrypted to ensure privacy and security within the network.

3. Range and Power Efficiency

   • Long Range: The LoRa technology enables communication over distances up to several kilometers, depending on the environment and antenna configuration.
   • Low Power Consumption: Meshtastic is designed to operate on low power, making it suitable for battery-powered devices and long-term deployments.

Use Cases

1. Outdoor Adventures

   • Hikers, campers, and outdoor enthusiasts can use Meshtastic to stay connected in areas without cellular coverage.

2. Emergency Situations

   • Meshtastic can be crucial in disaster scenarios where traditional communication infrastructure is damaged or unavailable.

3. Community Networks

   • Local communities can set up their own mesh networks for events, festivals, or local communication needs.

Getting Started

1. Hardware Setup

   • Purchase compatible LoRa modules and flash them with the Meshtastic firmware following the official guides.

2. Configuration

   • Use the Meshtastic mobile app or web interface to configure your nodes, set up encryption keys, and manage network settings.

3. Deployment

   • Deploy the nodes in the desired area and start communicating through the mesh network.

Conclusion

Meshtastic provides a versatile and robust solution for long-range, low-power communication. Its open-source nature and community support make it an accessible and practical tool for various scenarios where traditional communication methods are impractical.

2 - MQTT

MQTT is the technology used to feed the mesh data to the internet (aka what powers the Mesh Maps, Discord Logger, etc). Setting up MQTT is totally optional and should only be done on a staticly installed node with strong and reliable internet access (like a node on your roof). If you are just using a portable node, you do not need to take any actions.

MQTT Settings

If you want to use MQTT:

• Module Configuration > MQTT

  • MQTT Enabled: True
  • Encryption Enabled: True
  • JSON Enabled: False
    • This doesn’t work on RAK devices, only ESP32
    • Its limited and isn’t needed by the logger or meshview.
  • Map Report Enabled: Optional
  • Root Topic: msh/US/bayarea
    • EXACTLY this, the capitalization matters
  • Server Address: mqtt.bayme.sh
  • Username: meshdev
  • Password: large4cats
  • TLS Enabled: Optional
    • If you want to use TLS, it’s supported

• Radio Configuration > Channels > 0 / Primary

  • MQTT Uplink: Enabled
  • NEVER EVER ENABLE DOWNLINK

3 - Recommended Hardware

See also Discord #resources thread

Rak Wisblock

• Pros
  • Low power usage
  • Modular (Can easily add on gps and sensors)
  • Dedicated solar input
• Cons
  • Requires assembly
• Order from
  • Rak Wireless
  • Rokland
  • Etsy
  • Amazon

T Beam

• Pros
  • Fully built with display and gps (except battery and case)
  • Reliable
  • Somewhat cheap
• Cons
  • High power usage
  • Weird antenna placement
• Order from
  • Lilygo
  • Rokland
  • Etsy
  • Amazon

TTGo Lora

• Pros
  • Small form factor
  • Cheap
  • Already attached display and built in wifi and ble antenna
• Cons
  • No gps
  • High battery usage
• Order from
  • Lilygo
  • Rokland
  • Amazon

Wis Mesh

• Pros
  • battery efficient
  • Integrated gps
  • Nicest form factor
  • Fully built with case
• Cons
  • A bit expensive
• Order from
  • Rak Wireless
  • Rokland

4 - Recommended Settings

Please make sure to update the firmware on your device as you get started. The easiest way to do that is to use the Web Flasher. The latest stable release, even if labeled Beta, is generally a very safe option.

In the Bay Area, we have a few recommendations for configuration:

• LORA
  • Set region to United States (US)
  • Preset: Long Range - Fast (Default)
  • Number of hops: 3 (Default) - Please don’t turn this up.
  • Set Ignore MQTT to true to avoid forwarding MQTT traffic
• Channels
  • 0 Primary Channel
    • Name: Blank (Default)
    • Key: AQ== (Default)
    • You may wish to turn off Positions & Location if you’re not interested in broadcasting your location
• User
  • Long Name: Something descriptive. Ex: Your name, Discord Handle, or Ham Callsign
  • Short Name: Max of 4 characters, something unique for you and that particular radio. This will be what’s displayed in chat.
  • Licensed Operator: Do not enable unless you are a licensed Amateur Radio operators and have read Licensed Operations.
• Device Config
  • Device Role
    • Client Mute - Best for vehicles and anytime you have more than 2 nodes in the same place. It will not relay messages.
    • Client - Recommended for a home “base stations” or your single primary node. It will relay messages it receives.
    • Router / Repeater - Don’t use this to get started. There are a lot of considerations, and caveats, to using the offical Router & Repeater roles. Remember: The Client role relays messages just fine.
    • See offical docs for full breakdown
• Module Configuration
  • MQTT
    • If you want to be internet-connected, see MQTT - But this is for fixed position nodes, typically at home.
  • Device Telemetry
    • Device Metrics: 1 hour.
    • Sensor Metrics: 1 hour.