Documentation
Hoosier Mesh Documentation
Complete guides for setting up, configuring, and using Meshtastic devices on the Hoosier Mesh network.
Whether you’re new to mesh networking or an experienced operator, you’ll find everything you need to get the most out of your Meshtastic device in the Indiana community.
For New Users
Just getting started? Start here:
- Get a Node - Learn about different Meshtastic devices and choose the right one for your needs
- Getting Started - Step-by-step guide to unboxing, flashing firmware, and initial configuration
For Experienced Users
Need detailed configuration information? Check out these references:
Contribution Guidelines
Want to help improve the Hoosier Mesh network or this documentation?
- Contributing - Learn how to contribute to the Hoosier Mesh community and documentation
Quick Links
1 - Getting Started
Getting started with Meshtastic
Welcome to Hoosier Mesh. This getting started guide is broken into short steps
so you can move at your own pace.
Start here
- Start here - Safety, cables, and device basics
- Get a node - Hardware options and buying guidance
- Flash firmware - Drivers and the web flasher
- Initial setup - Core configuration for Indiana
- Use the app - Pairing and basic features
- Go further - Antennas, tools, and resources
- Local community - Maps, networks, and help
1.1 - Start Here
Safety checks and device basics before you begin
Before you begin
Critical Safety Warning
Never power on your device without attaching an antenna! Powering on the
radio without an antenna attached could damage the radio chip.
Verify your data cable
Before connecting your device to your computer, make sure your USB cable
supports both charging and data transfer. Some cables are charge-only and
won’t work for flashing firmware.
To verify your cable:
- Try connecting it to your phone or another device
- Attempt to copy a file to or from the device
- If file transfer works, your cable can also transfer data and is ready to use
Identify your board
Before you begin, decide on your first device. Check out the
Get a Node guide to help you choose the
right hardware for your needs and budget.
Once you have your device, identify its manufacturer and designation (for
example ESP32, nRF52, RP2040). You will need this information to select the
correct drivers and firmware.
Board name and designation: _______________________
Chipset overview
Meshtastic supports several chipset types, each with different advantages:
- ESP32-based devices: Equipped with WiFi and Bluetooth; ideal for web
interface access and WiFi configuration. ESP32-S3 variants offer improved
performance. Higher power consumption than nRF52.
- nRF52-based devices: Much more power efficient than ESP32; ideal for
battery-powered and solar deployments. Equipped with Bluetooth only (no WiFi).
Uses the UF2 bootloader for easy updates.
- RP2040-based devices: Dual-core ARM chip developed by Raspberry Pi.
Cost-effective for DIY projects. Use the UF2 bootloader and appear as flash
drives.
- Semtech-based devices: Choose newer SX126x or LR11xx series for improved
performance over the older SX127x series.
1.2 - Get a node
A list of potential nodes to get you started on your Meshtastic journey.
Ready to join the mesh? This guide will help you find the right Meshtastic device for your needs. Whether you’re looking for a portable tracker, a fixed solar repeater, or something in between, there’s a device for you.
Where to Buy
Official Partner Brands
These manufacturers produce officially supported Meshtastic hardware with excellent documentation and community support:
- Heltec - Popular ESP32-based devices, great for grid power
- RAK Wireless - nRF52-based WisBlock system with modular design
- Lilygo - Wide variety of ESP32 devices with screens and GPS
- Seeed Studios - Premium solar nodes and trackers
Community Supported Brands
Retailers
- Rokland - US-based retailer with good selection
- Amazon - Various models available with Prime shipping
Popular Device Models
Choosing a Chipset
ESP32: Better for grid-powered setups with WiFi access. Lower cost, more features, but higher power consumption.
nRF52: Better for battery/solar powered deployments. Much more power efficient, easier firmware updates via UF2.
General Purpose Devices
These devices are great for everyday use - portable, on-body, desktop, or vehicle mounting. They typically include screens, GPS, and good battery life.
| Brand | Model | Chipset | Best For |
|---|
| Heltec | V3 | ESP32 | Desktop/vehicle, WiFi needed |
| Heltec | V4 | ESP32 | Desktop/vehicle, WiFi needed |
| Heltec | T114 | nRF52 | Battery-powered handheld |
| RAK Wireless | RAK4631 | nRF52 | Modular builds |
| RAK Wireless | WisMesh Tag | nRF52 | Location tracking |
| RAK Wireless | WisMesh Pocket | nRF52 | Portable handheld |
| LowMesh | Pocket-S | nRF52 | Ultra-compact portable |
| Seeed Studios | T1000-E | nRF52 | GPS tracking |
| Seeed Studios | Wio Tracker L1 Pro | nRF52 | Advanced tracking |
| Lilygo | T-Beam | ESP32 | Popular all-in-one |
| Lilygo | T-Echo | ESP32 | E-ink display |
| Lilygo | T-Deck | ESP32 | Keyboard + screen |
| Lilygo | T-LoRa Pager | ESP32 | Compact pager |
| Lilygo | T-Watch | ESP32 | Wearable |
| Lilygo | T-Echo Lite | nRF52 | Battery-efficient |
| Elecrow | ThinkNode M5 | ESP32 | Affordable option |
| Elecrow | ThinkNode M1 | nRF52 | Affordable option |
| Meshnology | N37 | nRF52 | Custom design |
| Meshnology | N36 | nRF52 | Custom design |
| Meshnology | N30/N32/N33 | ESP32 | Various models |
| Meshnology | N35/N36 | ESP32 | Various models |
| Muzi Works | H2T | nRF52 | Premium handheld |
| Muzi Works | R1 Neo | nRF52 | Premium with GPS |
Solar Repeaters & Fixed Nodes
These devices are designed for outdoor installation, solar power, and long-term unattended operation. Perfect for extending network coverage.
Need Help Choosing?
- New to mesh? Start with a Heltec V3/V4 or RAK WisMesh Pocket
- Want maximum battery life? Choose any nRF52 device
- Need WiFi? Go with ESP32 devices like Heltec or Lilygo
- Building a repeater? Check out solar nodes from Seeed or Atlavox
- On a budget? Elecrow ThinkNodes offer great value
Still not sure? Ask for recommendations on the Indiana Mesh Discord!
1.3 - Flash Firmware
Install drivers and flash Meshtastic firmware
Browser requirements
Important
You must use Chrome or Microsoft Edge to access the Meshtastic
installer. Other browsers are not supported.
- Visit the Meshtastic website and navigate to the
Getting Started section
- Follow the instructions for your device type to download and install any
required drivers
Driver notes
nRF52 and RP2040 devices
These devices typically do not require serial drivers. They use the UF2
bootloader which makes the devices appear as flash drives. Do not download
USB device drivers unless required to install UF2 support.
- Only download serial drivers if your device requires them
- After installing drivers (if needed), restart your computer
Flash the firmware
- Return to the Meshtastic.org Getting Started
section
- Use the web flasher or follow the provided instructions to flash the
Meshtastic firmware onto your device
1.4 - Initial Setup
Core configuration for new nodes
Access the settings menu by pressing the settings cog icon. The recommended
configuration for nodes in the Indiana mesh network is documented in detail on
the Node Configuration Reference page.
Key settings to review:
- LoRa settings: Set region to US 915, preset to “Long Range - Fast”
- Channels: Configure the default “Long Fast” channel
- User configuration: Set your node name and long/short identifiers
- Device role: Set to CLIENT (or CLIENT_BASE for roof nodes)
- Position: Enable position broadcasting at 6-hour intervals
For the complete list of recommended settings for each category, see the
Node Configuration Reference.
Advanced configuration
For information on advanced configuration options including MQTT, Serial,
Telemetry, and External Notifications, see the
Advanced Configuration Guide.
1.5 - Use the App
Pairing and basic app features
Most people use the official Meshtastic mobile app to pair, configure, and
message from their node. Start with the official app and work through the
basic setup and pairing steps.
1.6 - Go Further
Antennas, tools, and helpful resources
Configuration guides
Upgrade your antenna
Once you’re up and running, consider upgrading your antenna for better range
and performance. Check what other community members are using and discover
options in the Meshtastic Antenna Reports
repository.
Maps and monitoring
Mobile apps
For more tools and resources, see the Resources page.
1.7 - Local Community
Maps, regional networks, and where to ask for help
Find nodes near you
Use these mesh maps to discover nodes in your area:
If you have a Discord account, you can also ask about other mesh users and
nodes in specific areas on the Meshtastic Community Discord.
Join other Indiana meshers on these regional networks:
Need help?
Have questions or found errors? Reach out on the
Indiana Mesh Discord or contact the community
members there.
2 - Contribution Guidelines
How to contribute to the docs
We use Hugo to format and generate our website, the
Docsy theme for styling and site structure,
and Netlify to manage the deployment of the site.
Hugo is an open-source static site generator that provides us with templates,
content organisation in a standard directory structure, and a website generation
engine. You write the pages in Markdown (or HTML if you want), and Hugo wraps
them up into a website.
All submissions, including submissions by project members, require review. We
use GitHub pull requests for this purpose. Consult
GitHub Help for more
information on using pull requests.
We welcome and encourage contributions from the Meshtastic community! Whether
you’re fixing a typo, adding documentation, or sharing your mesh networking
experiences, your input helps make this resource better for everyone.
Easy ways to contribute
Edit directly on the website
The easiest way to contribute is using the Edit this page button found in
the sidebar of every page on hoosiermesh.org. This
button takes you directly to GitHub where you can propose changes through a
simple pull request. No local development setup required.
What you can contribute
- Fix typos, improve clarity, or update outdated information.
- Add tutorials, guides, or configuration examples.
- Share information about local mesh networks or coverage areas.
- Contribute photos of node deployments or community events.
- Suggest new content or report issues.
Updating a single page
If you’ve just spotted something you’d like to change while using the docs,
Docsy has a shortcut for you:
- Click Edit this page in the top right hand corner of the page.
- If you don’t already have an up to date fork of the project repo, you are
prompted to get one - click Fork this repository and propose changes or
Update your Fork to get an up to date version of the project to edit. The
appropriate page in your fork is displayed in edit mode.
- Follow the rest of the Quick start with Netlify
process to make, preview, and propose your changes.
Creating an issue
If you’ve found a problem in the docs, but you’re not sure how to fix it
yourself, please create an issue in the
Hoosier Mesh repo. You can also
create an issue about a specific page by clicking the Create Issue button in
the top right hand corner of the page.
Quick start with Netlify
Here’s a quick guide to updating the docs. It assumes you’re familiar with the
GitHub workflow and you’re happy to use the automated preview of your doc
updates:
- Fork the Hoosier Mesh repo on GitHub.
- Make your changes and send a pull request (PR).
- If you’re not yet ready for a review, add “WIP” to the PR name to indicate
it’s a work in progress. (Don’t add the Hugo property “draft = true” to
the page front matter, because that prevents the auto-deployment of the
content preview described in the next point.)
- Wait for the automated PR workflow to do some checks. When it’s ready, you
should see a comment like this: deploy/netlify — Deploy preview ready!
- Click Details to the right of “Deploy preview ready” to see a preview of
your updates.
- Continue updating your doc and pushing your changes until you’re happy with
the content.
- When you’re ready for a review, add a comment to the PR, and remove any “WIP”
markers.
Previewing your changes locally
If you want to run your own local Hugo server to preview your changes as you
work:
Follow the instructions in Getting started to
install Hugo and any other tools you need. You’ll need at least Hugo
version 0.146.0 (we recommend using the most recent available version), and
it must be the extended version, which supports SCSS.
Fork the Hoosier Mesh repo repo into
your own project, then create a local copy using git clone.
git clone --branch v0.12.0 --depth 1 https://github.com/google/docsy-example.git
Run hugo server in the site root directory. By default your site will be
available at http://localhost:1313/. Now that you’re serving your site
locally, Hugo will watch for changes to the content and automatically refresh
your site.
Continue with the usual GitHub workflow to edit files, commit them, push the
changes up to your fork, and create a pull request.
Creating an issue
If you’ve found a problem in the docs, but you’re not sure how to fix it
yourself, please create an issue in the
Hoosier Mesh repo. You can also
create an issue about a specific page by clicking the Create Issue button in
the top right hand corner of the page.
Useful resources
3 - Reference
Configuration references and advanced guides for Meshtastic
These pages provide detailed reference information for Meshtastic node configuration and advanced features.
Configuration Reference Guides
3.1 - Node Configuration Reference
Complete reference for Meshtastic node configuration options
This page provides a comprehensive reference of all node configuration options recommended for the Indiana Hoosier Mesh network.
LoRa Settings
| Option | Setting |
|---|
| Region | US Region 915 |
| Use Preset | ON |
| Preset | Long Range - Fast |
| Ignore MQTT | OFF |
| OK to MQTT | ON |
| Transmit Enabled | ON |
| Number of Hops | 5 |
| Frequency Slot | 20 |
| RX Boost Gain | ON |
| Frequency Override | 906.875 |
| Transmit Power | 30 |
Channel Settings
| Option | Setting |
|---|
| Channel Name | Long Fast |
| PSK | AQ== |
| Uplink Enabled | ON |
| Downlink Enabled | ON |
| Position Enabled | ON |
| Precise Location | OFF |
| Distance Slider | 148 ft |
Security Settings
| Option | Setting |
|---|
| Direct Message Key (Public) | Populated* |
| Direct Message Key (Private) | Populated* |
| Log Serial Console | ON |
| Debug Log API | OFF |
| Admin Managed Mode | OFF |
| Legacy Admin Channel | OFF |
*Note: Unique to each node
User Configuration
| Option | Setting |
|---|
| Node ID | Populated |
| Long Name | Your Choice |
| Short Name | Your Choice (max 4 characters) |
| Hardware Model | Populated |
| Unmessageable | OFF (Optional ON for roof nodes) |
| Licensed Amateur Radio | OFF* |
Important: Meshtastic allows encrypted transmissions. However, US Amateur Radio licensing prohibits encryption. See FCC guidelines and our Amateur Radio & Meshtastic guide for complete details.
Device Settings
| Option | Setting |
|---|
| Device Role | CLIENT |
| Rebroadcast Mode | All |
| Node Info Broadcast Interval | Three Hours |
| LED Heartbeat | ON |
| Time Zone | Phone or GMT-5 |
| Button GPIO | 0 |
| Buzzer GPIO | 0 |
Device Role Notes
- CLIENT (default): Standard mesh participant
- CLIENT_BASE: Use for roof/attic-based nodes. Don’t forget to favorite your local owned nodes
- ROUTER / ROUTER_LATE: Avoid unless on a very tall tower. Check with experienced RF operators on the Indiana Mesh Discord before using these roles
Position Settings
| Option | Setting |
|---|
| Broadcast Interval | Six Hours |
| Smart Position | OFF |
| Fixed Position Lat | User Defined (via phone) |
| Fixed Position Long | User Defined (via phone) |
| Position Flags | 3 – User Defined |
| GPS Receive GPIO | Pin 0 |
| GPS Transmit GPIO | Pin 0 |
| GPS EN GPIO | Pin 0 |
| Altitude | Enabled |
| Altitude MSL | Enabled |
Serial Settings (Optional)
| Option | Setting |
|---|
| Serial Enabled | ON |
| Echo Enabled | OFF |
| RX | 0 |
| TX | 0 |
| Baud Rate | BAUD_DEFAULT |
| Timeout | 0 |
3.2 - Advanced Configuration - MQTT & Telemetry
MQTT, Serial, and Telemetry configuration for Meshtastic nodes
This page covers advanced configuration options for MQTT (internet connectivity), Serial interfaces, and Telemetry collection.
MQTT (Optional but Recommended)
MQTT allows you to access and control your Meshtastic nodes over the internet, integrating them with other services and creating mesh monitors.
MQTT Configuration
| Option | Setting |
|---|
| MQTT Enabled | OFF (optional ON) |
| Address | mqtt.meshtastic.org |
| Username | meshdev |
| Password | User Defined |
| Encryption Enabled | ON |
| JSON Output | OFF |
| TLS Enabled | ON |
| MQTT Root Topic | msh/US/IN |
Important MQTT Considerations
Network Overload Warning
When you enable MQTT, you’ll receive messages from many nodes across the network and can become overwhelmed with traffic. Use this feature deliberately and carefully.
Best Practices:
- Use MeshMap.net to check specific root topics of users in your area before enabling MQTT
- Consider the impact on your device’s performance and battery life
- Start with MQTT disabled and enable only when needed
- Monitor your device’s resource usage after enabling MQTT
Finding Your Root Topic
Check MeshMap.net to see what root topics other users in your region are publishing to. This will help you understand the network topology and choose an appropriate topic for your node.
Telemetry (Optional)
Telemetry allows your node to collect and broadcast device metrics like temperature, humidity, battery status, and GPS location.
| Option | Setting |
|---|
| Send Device Telemetry | OFF |
| Environment Metrics Module | OFF |
| Environment Metrics Update Interval | OFF |
| Environment Metrics On Screen | OFF |
When to Enable Telemetry
- Enabled by default on devices with environmental sensors
- Useful for nodes you want to monitor remotely via MQTT
- Increases power consumption on battery-powered devices
- Consider your use case before enabling
Serial/USB Configuration (Optional)
The Serial interface allows you to communicate with your Meshtastic device via USB or serial connection for advanced debugging and integration with external systems.
| Option | Setting |
|---|
| Serial Enabled | ON |
| Echo Enabled | OFF |
| RX | 0 |
| TX | 0 |
| Baud Rate | BAUD_DEFAULT |
| Timeout | 0 |
Use Cases
- Debug and monitor device behavior via serial port
- Integrate with external applications or sensors
- Advanced troubleshooting of device issues
- Integration with automations or home assistant systems
External Notifications (Optional)
Configure how your device alerts you to incoming messages.
| Option | Setting |
|---|
| External Notification Enabled | OFF |
| Alert message LED | ON |
| Alert message buzzer | OFF |
| Alert message vibration | OFF |
| Alert bell LED | OFF |
| Alert bell buzzer | OFF |
| Alert bell vibration | OFF |
These settings allow you to customize notification behavior based on message type and your preferences.
4 - Amateur Radio & Meshtastic
Information for licensed amateur radio operators using Meshtastic
Information for licensed amateur radio (ham) operators using Meshtastic devices. Understanding the legal and technical considerations is essential for compliant operation.
Important: Encryption & Licensing
Critical for Ham Operators
US Amateur Radio licensing specifically prohibits encryption of transmitted information. While Meshtastic supports encrypted communications, licensed amateur radio operators must disable encryption when operating under their amateur radio license.
See FCC Part 97 Rules for complete regulations.
Educational Presentation
For a comprehensive overview of Meshtastic for amateur radio operators, including legal considerations, technical details, and best practices:
📊 Meshtastic for Amateur Radio Operators - Google Slides Presentation
This presentation covers:
- FCC Part 97 regulations and compliance
- Encryption restrictions for ham operators
- Power output considerations
- Frequency allocations
- Proper station identification
- Technical configurations for licensed operation
Configuration for Licensed Operation
When operating under an amateur radio license, configure your Meshtastic device as follows:
User Configuration
In your node’s User Configuration settings:
| Setting | Value | Reason |
|---|
| Licensed Amateur Radio | ON | Enables ham radio mode |
| Long Name | Include callsign | Station identification (e.g., “KC1XXX - Josh”) |
Channel Configuration
Encryption Must Be Disabled
Default Meshtastic channels use encryption (PSK: AQ==). For ham operation, you must configure an unencrypted channel.
- PSK (Pre-Shared Key): Must be set to a default/empty value for no encryption
- Consider creating a separate channel for ham-only communications
Power & Frequency Considerations
Transmit Power
- Unlicensed: Limited to 1 watt EIRP (Effective Isotropic Radiated Power) on ISM bands
- Licensed: May use higher power levels within amateur radio band limits (check local regulations)
- Configure appropriately in LoRa settings based on your license class
Frequency Bands
- ISM Band (915 MHz): Available for both licensed and unlicensed use
- Amateur Allocations: Consult your local amateur radio band plan
- Ensure your device is configured for legal frequencies in your region
Station Identification
Per FCC Part 97.119:
- Station identification is required at the end of each communication and at least every 10 minutes during communication
- Include your callsign in your node’s Long Name for automatic identification
- Consider periodic position beacons to meet ID requirements
Power Output & EIRP
Understanding EIRP
Effective Isotropic Radiated Power (EIRP) = Transmitter Power + Antenna Gain - Cable Loss
Power Limits
- Part 15 (Unlicensed): 1 watt EIRP maximum
- Part 97 (Amateur): Varies by band and license class
- Technician: Check specific band limits
- General/Extra: Higher power privileges on most bands
Example Calculation
Transmitter: 30 dBm (1 watt)
Antenna Gain: +3 dBi
Cable Loss: -0.5 dB
EIRP = 30 + 3 - 0.5 = 32.5 dBm (≈1.78 watts)
For unlicensed operation, this would exceed the 1-watt EIRP limit.
Best Practices for Ham Operators
- Clearly mark licensed operation - Use callsign in node name
- Document your configuration - Note power levels, antenna specs, and EIRP calculations
- Separate licensed/unlicensed operation - Consider different devices or channels
- Join the community - Connect with other ham operators on Indiana Mesh Discord
- Stay current - FCC rules and interpretations can evolve
High-Power Station Options
For licensed operators seeking high-power operation:
- B&Q Station G2 - High-power licensed station designed for amateur radio use
- Custom Builds - Many operators build custom high-power stations with external amplifiers
Reminder
Always ensure your configuration complies with your license class privileges and local regulations. When in doubt, consult with your local amateur radio club or the ARRL.
Additional Resources
Questions?
Have questions about operating Meshtastic under your amateur radio license? Ask on the Indiana Mesh Discord where experienced ham operators can help guide you.
5 - Map
Our state wide map, powered by Mesh Monitor and built by the legendary community member Tranziq.