Post

@Edent I've been exploring LoRa as well. Here's my writeup about experimenting with MeshCore for a few weeks: https://mtlynch.io/first-impressions-of-meshcore/

Always a delight to be sent random circuit boards in the post 😄
Not sure I'll have enough time before #FOSDEM to set up a full #Meshtastic node, but I'll give it a go!

@Edent whichever one is prevalent around you. There could even be both. MeshCore is well suited for wide-area mesh networking. Meshtastic is more intended for personal ad hoc meshes, like when hiking, but it can be configured to work well in an infrastructure-based mesh. You can mostly reflash between the two so there’s little difficulty in playing with both. Each project has a Discord with local threads, and many areas have their own very substantial communities.

@Edent

I did a talk for the U of Michigan Amateur Radio Club on #meshtastic and the slides are on the WE8CHZ "MiRATS" site here

https://www.we8chz.org/wp-content/uploads/2026/01/Intro-to-Meshtastic-W8EMV.pdf

The fun you have with any mesh depends on the number of other people using the same tech locally.

Too few - frustration, talking to yourself
Acceptable -interesting local net with reliable paths
Too many - mesh network overload due to congestion

For actual emergency comms? Depends. Severe weather nets run on 2 meter / 70 cm ham repeaters.

@Edent my understanding is that meshtastic is older and possibly in more widespread use, but meshcore can probably do more?

I've used meshtastic a lot and found it to be servicible in my rural community. I am interested exploring meshcore, but chickens and eggs have to come first.

@Edent I prefer Meshtastic, but my local mesh switched to Meshcore. MC is not as good. It doesn't do as much. If you turn on a new node, it takes days to populated with the mesh nodes and half of them are unreliable links. I wasn't involved in the vote to switch.

Meshtastic has sensor integration and some simple stuff to get started. It's useful for IoT stuff. It quickly finds local nodes even factory fresh.

Both apps are quirky. Only one of them is open source.

@Edent
I saw a conférence about Reticulum (at CCC IIRC) and it looked very interesting, I don't know a lot about mesh so I have no adive but I would compare it to meshmatic

@Edent I'm on #meshcore because that looks to be more active in my area. (Netherlands)

I sarted with 25 euro investment for a helltec v3 (3.2 iirc) and I learned a ton about wireless signals already. I am planning to build a repeater to get the network more stable and put that out on the balcony where I live.

I'm having fun but it's still very new. It feels like proper emergency comms are still with the hams, but then I need to get a license.

Highly subjective takes, all of this. 😊Learning

@Edent I don't know if Benn Jordan has a presence on Mastodon, but I'm sure he'd have something to say on the subject. ..

https://www.youtube.com/watch?v=W_F4rEaRduk

@Edent I'd love to understand this too.

@Edent I've attended this seession a few days ago: https://techwerkers.nl/en/events/2026-01-15/

It was recorded.

They recommend MeshCore over Meshtastic.

@Edent I suspect that @alistairmacdonald may know a thing or two 😃

@Edent from my (limited) experience, Meshtastic is better for telemetry-sending, and messaging is a side effect that people have grabbed hold of. As a result short-range comms work well. Meshcore is designed to be more of a message relaying system. Meshcore also has much longer range because of the relays. The cluster I participate in reaches from Hull to Isle of Wight.

@Edent Neither are actually open source, I used Meshtastic for a year. Great for cities / festivals / mucking around.
Been using meshcore the last year or so.
Meshcore is MUCH more reliable for permanent setups, and usable for long range. We have like 200 meshcore nodes covering our whole state. Regularly messaging people hundreds of km away 12-14 hops.
This would be impossible on Meshtastic.

@Edent I would go with meshtastic because of the bigger reach in terms of community. Meshcore has cool functions, but it's not that big yet. BUT! Since they devices are pretty cheap, especially if ordered bare from china, why not both?

@Edent I'm much in the same boat with similar intentions so no real world experience yet.

I've got my eye on a couple of Heltec v4 devboards. v4 because they support gnss which is interesting for a few 'fun' use cases I have with friends and while it seems Meshcore is the way to go in NL as its more widely used, I understand incan switch to meshtastic pretty easily using same hardware.

Heltec appear to have decent shipping methods from their own site but I've seen similar if not exactly the same ones on usual suspect large online retail shopfronts.

@Edent I've so far stuck to meshtastic because it seems more, well, meshy. My use case doesn't include joining a wider local mesh so it's exactly what I need.

If you're usecase is joining a wider local mesh then you have to go with the (local) crowd, which you'll probably need a non-mesh network to find out about. Probably Facebook but who knows!

I'm currently using Sensecap and RAK card devices which work pretty well.

@Edent MC is good for a pretty much static infrastructure if you have reliable and stable repeaters and want to reach long distances. MT is better for ad-hoc networks for a limited area (a town or an event for example) where you can't rely on semi-permanent repeaters.

@Edent Keep in mind that many hardware devices could run #meshcore as well as #meshtastic. So you could try one mesh and still switch if you revise your decision.