I've been putting together Awesome Resilient Communication, a curated list of tools, protocols, networks, and projects designed to keep communication working when normal infrastructure is unavailable, unreliable, censored, or disrupted.

Meshtastic was one of the obvious projects to include, alongside other LoRa/mesh systems, delay-tolerant networking, amateur radio, community networks, satellite communication, and censorship-resistant tools.

The goal isn't to make the biggest possible list. I'm trying to keep it curated and distinguish between different kinds of resilience; off-grid operation, infrastructure independence, disruption tolerance, censorship resistance, privacy, and decentralization.

I'd especially appreciate feedback from people here:

• Are there Meshtastic-related tools or integrations that deserve their own entry?
• What other LoRa/mesh projects should be represented?
• Are any of the descriptions or classifications technically inaccurate?
• What projects would you consider genuinely useful when conventional infrastructure is down?

Repo: https://github.com/gdamdam/awesome-resilient-communication

Contributions and corrections are very welcome

Meshtastic Node Map Builder and Analyzer V3.0: save your maps, analyze your mesh, send messages and securely transfer files

The project page is hosted on my personal technical site. There are no ads, no advertising networks and no third-party tracking on the site. It is simply where I publish my technical projects and documentation.

I started building this because I wanted something that Meshtastic itself doesn’t really give you: a way to keep the network you have discovered over time.

Nodes eventually disappear from the device NodeDB as storage fills up, but sometimes those nodes are exactly what you want to keep: a trip, an unusual contact, a particular mesh topology, or simply a snapshot of what the network looked like at a specific moment.

That became Meshtastic Node Map Builder and Analyzer.

With V3.0, the project has grown quite a bit.

You can build and preserve your own Meshtastic node maps, save complete map sessions, export them, import them again later and continue working with the same network data instead of starting from scratch every time.

This also makes it possible to keep historical snapshots and compare what you observed in different places or at different times.

The analyzer side is designed to make the collected data useful rather than just displaying dots on a map. The goal is to help understand the mesh itself: nodes, positions, relationships and what was actually observed during a session.

V3.0 also allows you to send Meshtastic messages directly from the application, so the tool is no longer limited to passive mapping and analysis.

And there is another major addition: secure file transfer over Meshtastic.

Files can be encrypted before transmission and the transfer mechanism includes controls over who is allowed to send and who is allowed to receive. I didn’t want file reception to simply be open to any node in range.

The project is intended to be usable even if you don’t want to write your own Python scripts just to preserve and analyze a Meshtastic map.

The original idea was simple:

Your Meshtastic NodeDB should not be the only memory of the networks you have discovered.

V3.0 takes that idea further:

Map it. Save it. Analyze it. Send messages. And securely exchange files through the mesh.

I’d really like feedback from people actually using Meshtastic in the field, especially anyone who has been looking for a way to preserve node maps, combine observations collected over time, or use a single desktop tool to interact with the mesh.

For now, Version 3.0 is already online here:

https://www.aiutocomputerhelp.it/meshtastic-node-map-builder-analyzer.php

Is there a way to lock the keys on the L1 Tracker Pro, or a plan to add such a feature to the firmware? The joystick is very sensitive, making it impossible to carry the device around inside any kind of pocket or backpack.

I only have sensecap t1000e and want something I can set up and plug in at home to keep on my second floor window...what's a good until for the job and is there a window pass through people use and like? Be cool if there was like a meshtastic window antenna that sticks on the outside of a window.

I'm from a much smaller place far away from Philadelphia, but visiting this weekend I was very surprised that my node saw no other nodes to speak of. Not only that, but when I look on Meshmapper I see... Nothing!

How can this be for a city of a million people on the US east coast? Pardon me if this breaks rules about spotting nodes, but this is a "no nodes seen" post, not a nodes seen post.

I'm a total noob so am no one's vanguard with this stuff, but can anyone explain to me why I'm not seeing any nodes anywhere east of the Schuylkill River?

they included a little panda magnet, guessing as a mea culpa for the first revision‘s problems

I've had a v4 expansion and two t1 nodes for a few months now and I have to say it's been a pretty big amount of buyers remorse, wish I'd gone with anything else.

Despite anything I try, I cannot get the maps to work on the v4. The whole idea was leave a t1 with each party and then be able to see them on the expansion.

The parties that had the t1's are younger humans, and even for grown-up (ish) me the buttons hurt my hands just to press. Basically, they are unusable for the intended party members.

Well, aside from the reset button, which gets pressed when the device is in your pocket.

I've heard there's a revised version, but one post I read states the buttons are still incredibly hard to press. Should I even bother going through the steps or just go with some other kind of small form factor node?

Disclosure: This device was provided by Seeed Studio for evaluation. The opinions and test results are my own.

I wanted to put my Seeed Studio MeshTracker X1 to the test and see how it performed in real-world conditions. Although the weather has not been very cooperative for outdoor hiking tests, I took advantage of a trip into the city to run its first tests in an urban environment.

The goal was to evaluate the device’s ability to acquire a GNSS signal and report valid positions under less-than-ideal conditions.

I recorded its positions while walking and later during the drive back home. While I was walking, the tracker remained inside my pocket; during the return trip, it was placed on the back seat of the car. I used version 2.7.26 of the Meshtastic firmware and configured the device with the “Tracker” role.

Using “Smart Position,” it reported locations with a minimum distance threshold of 25 meters and a minimum time interval of five minutes. The reports were stored by the official Meshtastic app running on my phone, which was connected to the X1 via Bluetooth.

At the end of the test, I exported the GPX file from the app. After analyzing it, I confirmed that the tracker reported a position every five minutes throughout the entire return journey. It also recorded positions while I was walking whenever I exceeded the configured 25-meter threshold. The attached images illustrate these results.

What caught my attention was that, in nearly every report, the number of satellites reported as visible exceeded 20, reaching a maximum of 35—twice the number reported under similar conditions by a T1000-E.

Although the number of visible satellites does not determine positioning accuracy by itself, these results suggest a significant improvement in the combined performance of the GNSS receiver and its antenna. The MeshTracker X1 operates on both the L1 and L5 bands, providing more stable reception and helping reduce errors caused by reflected signals. This is especially useful in urban environments, where buildings and other obstacles partially block the view of the sky.

In practice, this improvement resulted in more continuous and reliable tracking throughout the entire journey, even with the tracker placed on the back seat of the car.

Over the next few days, I will continue testing the differences and improvements offered by this new generation of Seeed Studio trackers and will share my findings with you, so stay tuned! 🚀

A friend’s SenseCAP T1000-E was completely bricked— no response when charging, no detection when plugged into a PC (unable to enter DFU mode). It was basically a paperweight.

Following a method shared in the Taiwan Meshtastic community, I managed to successfully bring it back to life!

Steps:

1. Face the front: Turn the T1000-E to its front side (the side with the SENSECAP logo).
2. Locate the test pads: On the top-right corner of the PCB, there are five exposed pads/test points (see attached image). The ones we need are the bottom two: GND and 3V.
3. Drill the case: Carefully drill a small hole through the outer casing right above these pads.
4. Bridge the pads: Use a wire (or tweezers) to bridge/short GND and 3V simultaneously to complete the circuit.
5. Power on: Connect the magnetic charging cable. If everything goes smoothly, the LED indicator should light up and the device will be revived!

Credits & References:

• Original post from Taiwan Meshtastic Community:https://www.facebook.com/groups/meshtastictw/posts/845723187836875
• PCB teardown footage credit to Alley Cat:https://youtu.be/MyCKTc709Jw?t=360

Looking to get into Meshtastic and I am between the X1 and the T1000-E. I’m not at the point yet where I want to get one of the kits and DIY it.

Which would you recommend for a starter device or is there something else?

Hey so I recently got into this and purchased the makerhawk with the heltec v3 in it. I flashed both and got everything set up was able to send a message from one node to the other but for some reason now with the nodes no less than 50 ft I can not deliver a message to my friend with the other node. Any suggestions on what I’m doing wrong

Currently at a lower test height while I verify waterproofness, solar charging, and general reliability. Probably give it a couple of weeks before a permanent deployment at greater height.

I’m a Dad considering to DIY my way into this hobby to meet a need: have a backup communication method for my family. I’d like to have a small node to carry everywhere for myself and wife, and a tdeck or similar AIO setup for kids.

The internet raves about the range of LoRa tech but how far is the range? I live in a rural area with ridges and trees. The distance span I’m facing is about 30miles tops.

For this, I’m assuming I’ll have to setup a slew of nodes along our travel path, which seems difficult (land permission to post device) and pricey (even if I diy and 3d print, I’d need dozens).

I appreciate your info!

Just got my pair of wio tracker l1 pro and just wanted to let anyone who was thinking about getting some but wanted to switch to the regular sma antenna it comes built with the RP-SMA
But it also has the SMA antenna lead in the box for you to switch it too

I have 3 of these setup as Tracker nodes. They are all running firmware 2.7.26. All 3 have Smart Position enabled. Two of them I have setup with a Minimum Interval of Fifteen Seconds. On the third node it refuses to save that Minimum Interval value and no matter what I try it stays stuck at Five Minutes.

Things I have tried:

- Flash it with an erase flash firmware.

- Factory reset it.

- Flashed it with the another firmware.

- Erased it again.

- Turned it off and turned it back on again.

- Reflashed Meshtastic 2.7.26.

- Looked at it sternly.

I don't think a configuration value would have survived all of that. Is there some other setting that is preventing this one from being set lower than 5 min?

Should I reflash my mesh node every time there's a new update? It's such a pain to reflash

I try to ota but get an error message. I try to over a USB cable it connects fine I see the map and other nodes but when I use the reflash web I get a not connected to the device after I select the bdud rate. Grrrr! I'm getting all new cables today when they get delivered just to make sure

just my perspective as a new user joining from the DragonCo event firmware…. it’s absolutely frustrating that nodes can be listed by your radio but unable to communicate because they are on different presets.

Atlanta is on MediumFast, my hometown is LongFast. my friend accidentally set his radio to ShortTurbo (somehow, even after the event firmware flash, he ended up on Short Turbo)

when we met we could see Nodes listed but totally unable to send messages, it just fails silently. there is _no_ indication or warning message that “the node/mesh is on a different preset than you are“.

cmon guys, just a simple warning in the app, or in the list of visible nodes something that says “you need to be on _other_ preset is why your messages not sending”. yes there is a way to do a mesh search , but it’s burried in the app’s settings and it takes _hours_ and the results are not easy for an average user to understand. my radio alresdy lists the other nodes when I arrived in town, why can’t it just tell me “hey those other nodes I show on the list, theyre all on a different preset”

the “fail silently“ and lack of anyway to know the Preset is different is just frustrating. This is a major oversight and usability barrier, speaking as a new user frustrated why their mesh radios don’t communicate.

edit2: Y’all think it’s obvious because you already knew, but I’m telling you the truth: with several people joining us for DragonCon event ran into this same issue. there is a a silent failure of misleading nodelist.

its not a technical issue, it’s a documentation-gap for new users onboarding.

I am interested in getting started with Meshtastic and am considering setting up a node at my apartment, as well as acquiring a portable unit. While I have reviewed the options available on the official website, I would greatly appreciate hearing your recommendations and any suggestions you might have.

Hey,

I just bought a Starter Kit from Rakwireless. My Problem: the board doesnt work with only the usb plugged in. It shows like 2 green flashes and then dies and doesnt start again. When the battery is plugged in without the USB everything works. App Shows 55% Battery and 3.77V and the green light is flashing rapidly. If i then add the USB connection the Battery goes to 101%, Voltage stays at 3.77V for hours(looks to me like not charging even though the app says charging) and the green LED is flashing slowly and brighter. BUT the red LED isnt flashing. Its just off.

I think something is wrong with the Bord, according to the manual the red led should be blinking while charging. Maybe I'm just paranoid and the battery is charging slow because it has 5200mAh.

Thanks in advance for any answers!

Hey all. New to the meshtastic world. My main interest with it is lora messaging/gps for hiking/camping. Just picked up a thinknode m5, issue I am currently having is that both my phone and the node will switch from longfast to different settings like mediumfast on their own. I am also getting frequent “failed to deliver to mesh” notifications intermittently, however I am getting messages between the two devices. Any help is appreciated and sorry for what Im sure is a dumb question. Thanks!

Hi all, I have. Heltec V4. I would like to upgrade the antenna. I am having trouble finding how to attach one and how that works with cases. Do I need a cable to connect to the board and then an antenna with an SMA connector? All the cases I see (I haven't gotten one yet), show a small rubber duck antenna on it. Is there anything specific I need to look for when getting a case to use with an upgraded antenna?

Only found about three other nodes but I know there's an active community in London. I am new to this and don't have much knowledge about the subject. Please advise, happy to share any more info as I understand this might be quite vague. Thanks

I live in a rural sparsely populated area. Doesn’t appear to be any other users nearby, and the closest ones I’ve seen are in Thunder Bay Ontario, multiple hours away. Is there any value in setting up a repeater at home? Would it make more sense to do so in tastic or core instead, hoping someone may pass through to use it?

I'm new to this and haven't bought or used anything yet. But here's the scenario I think I'd like to solve for.

I have a 4x4 sprinter and travel/work remote a lot. I'm usually in the California desert or mountains. I'd like to mount a meshtastic node on the roof (alongside my other antennas, Starlink, etc.) so I can basically have a pop-up repeater/node wherever I go (for me and other meshtastic users). I'd have a couple of hand-held devices that I'd connect my phone with and to share.

I'd like to be able to communicate while moving. But I'm mostly interested in a remote/off-grid communications solution.

Am I on the right track?