Firmware and Software FAQ How do I update my Meshtastic firmware? The Easy Way: Web Flasher The Meshtastic web flasher at flasher.meshtastic.org handles everything automatically. It works in Chrome and Edge (Firefox does not support WebSerial). Connect your device to your computer via USB Open flasher.meshtastic.org in Chrome or Edge Click "Connect" and select your device's serial port The flasher auto-detects your board type and shows the latest stable release Click "Flash" and wait 2-3 minutes for the process to complete The device reboots automatically when done Your configuration is preserved during a normal update. Settings stored in flash persist through firmware updates in most cases. However, major version upgrades (e.g., 2.2.x to 2.3.x) may reset some settings - always export your config before a major update. Exporting Config Before Updating meshtastic --export-config > my-node-config.json This saves all your settings to a JSON file. If the update resets your config, restore with: meshtastic --import-config my-node-config.json Over-the-Air (OTA) Updates Meshtastic supports OTA firmware updates via Bluetooth on ESP32 boards running firmware 2.1+. In the Android app: go to the connected device settings and look for "Firmware Update" if available. This is convenient for nodes that are accessible but not near a computer. OTA is not available on nRF52840 boards (T-Echo, RAK4631) - these require USB flashing. How Often Should I Update? For personal devices: update when you want new features or bug fixes. There's no urgency unless a security issue is announced. For community infrastructure nodes: test new firmware on a non-critical node first, then coordinate with the community before updating. Avoid updating repeaters mid-event or during high-use periods. When NOT to Update During an active emergency operation - never update infrastructure during an event If your network is working well and other nodes are on older firmware - major version jumps can cause compatibility issues until all nodes update Right before a planned use - allow 24 hours to discover and fix any update-related issues What Meshtastic firmware version should I run? Always Run Stable Releases on Infrastructure Meshtastic releases three types of firmware builds: Build Type Stability Use for Stable (e.g., 2.3.14) High All production nodes and community repeaters Beta (e.g., 2.3.15.beta1) Medium Personal testing nodes only Alpha / Nightly Low Developers only; may have breaking bugs Version Compatibility Meshtastic maintains backward compatibility within a major version (2.x). All 2.x nodes can communicate with each other, though newer firmware may use packet formats that older firmware ignores. Avoid running 1.x firmware anywhere on an active 2.x network - it is not compatible. The PKI Direct Messaging feature introduced in 2.3 requires both nodes to run 2.3+ for encrypted DMs. Mixed networks (some 2.2, some 2.3) still work for channel messages; only DMs between 2.3+ nodes get PKI encryption. Checking Your Current Version In the Meshtastic app : Settings → About, or check the device info screen. Via CLI: meshtastic --info | grep Firmware Upgrading a Community Network For coordinated community upgrades across multiple repeaters: Announce the planned update in your community communication channel Update one non-critical repeater first and test for 48-72 hours If no issues, update remaining repeaters in off-peak hours (late night) Document firmware versions for each node in your network inventory How do I factory reset my node? When to Factory Reset Factory reset clears all configuration and returns the node to out-of-box defaults. Do this when: You've changed so many settings that the node misbehaves and you can't identify the cause You're repurposing a node from one network to another and want a clean start Selling or giving away a node (removes your channel keys and personal info) As a last resort after troubleshooting fails Via the App In the Meshtastic Android/iOS app with the node connected: Settings → Device → Reset Node DB (resets node database only) or Factory Reset (clears all configuration). Via CLI meshtastic --factory-reset This clears all radio configuration, channels, and user settings. The node reboots and appears with default settings. Note: this does NOT clear the firmware - you will still be on the same firmware version after a factory reset. Via Hardware (Button) Most boards support a hardware factory reset by holding the user button during power-on, or pressing it a specific number of times. Check the Meshtastic documentation for your specific board model. The hardware method is useful when you can't connect to the device via Bluetooth or USB. What Factory Reset Does NOT Do Does not change the firmware version Does not change the hardware node ID (derived from hardware keys, not erasable) Does not affect other nodes on the network - their node databases will still have a record of your node until it ages out After a Factory Reset You'll need to reconfigure everything: region, channel, role, position (if fixed), and any module settings. If you exported your config before resetting, restore it with: meshtastic --import-config my-node-config.json If you're joining a community network, obtain the channel QR code or URL from the network coordinator and scan/tap it to configure your channels automatically.