Meshtastic promises communication without a network—a concept that excites outdoor enthusiasts, emergency planners, and event organizers alike. Affordable LoRa nodes are supposed to carry messages even where no cell signal exists. But as enticing as the vision sounds, reality lags behind. Reliable messaging remains the Achilles' heel of this otherwise fascinating project. What is going wrong? And how could it improve?
1. Messages that disappear into thin air
Meshtastic promotes itself as a “long range off-grid communication platform,” yet in practice, messages often vanish without a trace. In real networks, they don’t appear in the app or are only partially confirmed. Especially iOS users report lost messages after connection drops—reboots are often the only fix, which is frustrating. Community forums like Reddit are full of complaints: “I see nodes, but hardly any replies come through.”
Sources:Reddit,GitHub Issues
2. Acknowledgments that don’t guarantee delivery
Acknowledgments (ACKs) are supposed to ensure messages arrive—but they are unreliable. As early as 2021, there were discussions about “acks getting starved,” and even in 2025 users are calling for "Double ACKs" to provide clarity. Since the core promise is "messages get delivered," Meshtastic falls short here.
Sources:GitHub Issues
3. Apps that test the user’s patience
The Meshtastic apps add to the frustration: empty message windows, missing notifications for direct messages, or advice to reinstall the app. Although there are regular fixes, users often feel like beta testers. Developers are working on it, but a polished user experience is still missing.
Sources:Reddit,GitHub Issues
4. Hardware: Lots of options, little refinement
Meshtastic supports a wide range of devices – but “supported” does not mean “optimized.” For example, the LilyGO T-Deck Pro only gained visible support in 2025 (firmware v2.7.4), and that support is not mature. The larger display is ultimately underused, there's no keylock for a device with a touchscreen, etc.
Sources:Reddit,Meshtastic Docs
5. Scaling: When the network gets overloaded
Large Meshtastic networks quickly hit limits. The developers themselves warn about channel congestion caused by incorrect router profiles (e.g., ROUTER_LATE) or overly “chatty” presets like LongFast. Collisions and packet loss render the network unusable. Community threads show that scaling remains an unsolved challenge.
Sources:Meshtastic Blog
6. Telemetry: More noise than benefit
By default, nodes regularly send telemetry data (e.g., positions, environmental info) — often every 30 minutes. While it sounds like useful monitoring, it clogs radio frequencies, especially in dense networks. The community discusses throttling, and official documentation recommends longer intervals. Yet default settings are often too aggressive, straining messages and battery life.
Sources:GitHub Issues,Meshtastic Docs
7. Battery life: Efficient only in theory
LoRa is considered low power—but only if little is transmitted. In active networks with many broadcasts or router relays, power consumption rises rapidly. Documentation recommends power-saving profiles; external guides suggest aggressive intervals or disabling unnecessary features. Battery life heavily depends on how "quiet" the network is—and it rarely is.
Sources:Meshtastic Docs,Heltec Docs
8. Empty chats despite full networks
In urban “Open Channels,” many nodes are visible—but conversations are scarce. Reasons include unreliable delivery, overloaded channels, and app sync issues. The result is a paradoxical experience: it feels like a network, but communication remains patchy.
Sources:Reddit
Conclusion: A project with potential, but lacking polish
Meshtastic is an impressive, community-driven project with rapid development. However, the vision of reliable off-grid messaging is still unmet in 2025. The biggest hurdles:
- Reliability: message loss and insecure ACKs.
- Apps: bugs and synchronization problems.
- Hardware: broad support but often immature platforms.
- Scaling: large networks hit limits quickly.
- Telemetry: too much data traffic stresses networks and batteries.
What would help?
- More robust delivery: improved ACK strategies and confirmed retries.
- Stable apps: fewer bugs, clean synchronization.
- Conservative defaults: longer telemetry intervals, power-saving presets.
- Clear scaling advice: avoid LongFast, use lean router profiles.
- Device transparency: a clear “tier list” for hardware (e.g., Gold/Silver/Beta).
Until these issues are addressed, Meshtastic remains an exciting experiment—not a reliable “off-grid WhatsApp.” Users wanting production use should keep networks small, throttle telemetry, and expect outages.
Meshcore: A lean alternative
An interesting comparison is Meshcore, a lesser-known project focused on essentials: messaging. No telemetry flood, no overloaded features. Routers efficiently forward messages; clients communicate directly with them—not device-to-device as with Meshtastic. This makes Meshcore more stable: messages get through reliably, chats run smoothly. The downside? Meshcore has a smaller community, less device support, and a less dynamic ecosystem. For pure off-grid messaging, it is often the more robust choice.
Sources
- Meshtastic Docs & Blog: Off-grid claims, router/preset notes
- GitHub Issues: ACKs, message loss, app bugs
- Reddit: user reports
- Heltec Docs: battery tips
- Meshtastic device notes: T-Deck Pro support