Meshtastic excites DIYers and outdoor enthusiasts because it enables communication without cellular reception or Wi-Fi. Using simple LoRa modules, a mesh network is created that can send messages over long distances — at least in theory. In practice, however, things often go wrong: messages don’t arrive, are displayed incorrectly, or the system malfunctions inexplicably.
Messages Disappearing Into Thin Air
A major issue is unreliability. Some messages get lost, even when devices are only a few meters apart. Direct messages between two nodes (devices) often don't work as intended. Even more confusing: sometimes a message appears on the device's display but not in the smartphone app. Users then assume the message is lost, even though it is actually stored on the device. This causes frustration and the impression that the network is broken.
Empty Messages and Cryptic Gibberish
Another annoyance is so-called "Empty Messages." In the app, a message appears blank even though text was actually sent. This happens occasionally at random, more frequently after firmware updates, or when different app versions are used. Even worse: instead of readable text, sometimes cryptic symbols or unintelligible gibberish appear. To users, it looks like messages are corrupted, although most often the software is at fault, not the radio signal.
Radio Congestion and Delays
Small networks with only a few devices often run stably, but larger meshes quickly run into trouble. When many messages are sent simultaneously, collisions occur. LoRa is designed for range, not speed, which means each data packet blocks the radio channel for a long time. This causes delays, lost messages, or texts arriving minutes later.
Choosing the radio profile is crucial. Profiles intended for long distances occupy the channel longer and increase the risk of interference. In busy networks, this leads to a kind of radio traffic jam.
App and Device: Two Different Worlds
Connection between the device and the app also causes problems. Nodes are often detected in the network but don’t appear in the app. Status messages like "last seen" are frequently outdated or incorrect. Users see something different on the device than in the app. Together with empty messages and gibberish, this creates the impression the system is unusable — even though data is often exchanged in the background.
What’s Behind This?
The issues have several causes:
- LoRa technology: Long transmission times and low data rates lead to collisions.
- Limited storage: Devices can only store a limited number of other nodes. In large networks, older entries get displaced, causing errors.
- Encryption and routing: Private messages use more complex processes that are more secure but also more error-prone.
- App integration: The apps are still under development, leading to display or synchronization issues.
Tips for More Reliability
Despite the weaknesses, there are ways to optimize Meshtastic:
- Choose a faster radio profile to reduce transmission time.
- Split large networks into smaller groups to avoid overload.
- Use stable firmware and app versions rather than experimental updates.
- Restart or reinstall often helps with display problems.
- Deploy additional "store-and-forward" nodes that cache messages and forward them later.
Conclusion
Meshtastic has huge potential but is not yet mature. Messages disappear, show up empty, or appear only on the device but not in the app. In larger networks, radio collisions and overload add further difficulties.
Still, the project is continuously improving. Users with patience and who adjust their settings can already build a functional off-grid network — even if it’s not as reliable as traditional cellular networks. With some fine-tuning and realistic expectations, Meshtastic can be a lot of fun!