Search Results

Why Duplicates Happen Duplicate messages in Meshtastic are normal and expected - they are a feature of flood routing, not a bug. When a node receives a message, it rebroadcasts it. If you're within radio range of multiple nodes that each received and retransmi...

What Channel Utilization Means Channel utilization is the percentage of time the LoRa radio channel is occupied by transmissions. It's displayed in the Meshtastic app as a percentage (visible in the channel info or device telemetry). Think of it like a single-...

Picking the right enclosure is one of the most consequential decisions in any outdoor LoRa build. A node that works flawlessly on your workbench can fail within weeks if rain, dust, or condensation reaches the electronics. This page walks through IP ratings, c...

The gasket between the lid and body of your enclosure gets all the attention, but cable penetrations are among the most common ingress failure points in outdoor electronics. Cable penetrations are a more common water-ingress path than a properly maintained lid...

A perfectly sealed enclosure with no cable gland defects can still suffer moisture damage from condensation. This page explains why condensation occurs in sealed enclosures and the proven methods to prevent it. Why Condensation Happens When you seal an enclo...

Heat is the silent killer of outdoor electronics. A node that operates flawlessly through rain and vibration can fail within months if it repeatedly reaches thermal extremes inside its enclosure. This page covers the mechanisms of solar heating, its effects on...

This page consolidates the step-by-step procedures for assembling and commissioning a sealed outdoor enclosure, along with a maintenance checklist to keep your nodes running reliably year after year. Step-by-Step Enclosure Assembly Step 1: Dry-Fit All Compon...

Meshtastic provides several device roles for infrastructure nodes that exist to extend network reach rather than serve end users. On current firmware the relevant roles are ROUTER, ROUTER_LATE, and REPEATER (with CLIENT being the right choice for the overwhelm...

The hop limit is one of the most important and most misunderstood parameters in a Meshtastic mesh. Setting it correctly reduces unnecessary rebroadcasts, controls how far a message propagates, and prevents broadcast storms that saturate the channel. This page ...

A repeater node that knows its own location serves the community in two ways: it appears accurately on coverage maps, and it lets neighbouring nodes calibrate their own position estimates. Without a fixed position, a GPS-less repeater either appears at coordin...

A repeater deployed on a hilltop or building rooftop is useless to the community if failures go undetected for days. Effective remote monitoring lets you catch power issues, firmware hangs, and hardware faults before users notice. This page covers the monitori...

Meshtastic has no over-the-LoRa firmware push between mesh nodes - firmware cannot be sent from one node to another over the radio mesh. Firmware is updated via a USB connection to the device, or via Bluetooth OTA on supported nRF52 devices (e.g. RAK4631). For...

Infrastructure repeaters are expected to operate unattended for months. When behaviour deviates from normal - excessive channel utilisation, duplicate node entries, relay failures, or complete silence - rapid and systematic diagnosis avoids unnecessary site vi...