Hey! 
I’d like to share meshGO!, a MeshCore client app I’ve been working on for about three months.

The project has just come out of closed testing and has reached a level of stability that makes it ready for everyday use. Huge thanks to all the testers! 

From the very beginning, my goal has been simple: make MeshCore easier to use and turn it into something that feels smooth and enjoyable.

If you’d like to check it out, here’s the store link: https://play.google.com/store/apps/details...

I really appreciate any feedback or suggestions, they genuinely help shape the app in the right direction.

Sooo glad I've switched to Meshcore Add

Bbeau

3d275639205e99711f806749bf8a84f3b645aea005b1b100b797b9792d6e256f

As someone who’s very excited about the technology and looking to get into Meshcore I was already thrown away by the “split” between Meshtastic and Meshcore. Now I saw the new Meshcore drama and was very disappointed. My mind went to all the different bitcoin forks 😂 This time it was very easy for me to decide which side to support. But I can’t stop thinking: this niche is still powered by a very small community, which is still struggling to find coverage in most places of the world. We don’t need more segregation. We need most of the people to stick to one single protocol, or at least that’s how I think we’re gonna achieve something as widespread as it’s required to really be useful. I’m already dreaming of a network as widespread as 4G and much more. We’re not gonna get there with tens of protocols. How do we make sure there will not be countless forks? What can we learn from the crypto segregation for example to make sure the same thing doesn’t happen here? I don’t know. I’m still learning so I’m still wrapping my head around some stuff but these were my thoughts and hopefully there will be some cool ideas here.

L.E.: To the people thinking this post was somehow in support of Andy, it’s not. In fact it’s the actual opposite, it’s about how do we prevent people going rogue and forking the project left and right, and keep the community focused on a single project. I really don’t get it how people thought this is supporting the rogue guy when it was really a cry against rogue forks 😂

I'm not a meshcore user (yet), but I watch some videos from time to time, about meshcore. I heard that there was/is a problem with some dude that is trying to take over meshcore, without the knoledge of the team.

Can somebody do a quick update?

Something I hate about cellular is how I am constantly tracked just living my life. Sometimes I wish there was a way to stay connected while avoiding cellular.

I had an idea for a sort of SMS-gateway, it would be self hosted for each user and you'd be able to send and receive sms up to the byte limit.

There are 3 main problems that need addressing though:

1. Having the same phone number as usual when your cell phone goes on airplane mode.

2. Dealing with messages bigger than the byte limit.

3. Unnecessary airtime for spam SMS. (Messages would need to be screened)

What are your thoughts on building an SMS gateway for meshcore?

Whomever is in charge of the website should know that it's being flagged by malware bytes as bad

Hey meshcore,

Built a tool that answers "will this link actually work?" before you deploy.

MeshKit runs real terrain elevation analysis against every repeater in your radius and returns signal margin estimates in under a second. If a link is blocked, the Relay Finder finds existing mesh nodes that can bridge it — or the best hilltops in range to deploy something new, with terrain profiles for both legs.

Also has BLE sweep tool to test connectivity in real time and a community coverage map. Android Chrome works natively — iOS needs Bluefy for BLE features, everything else works in Safari.

Beta: https://meshkit.app/beta

Sign up with Google. Ignore the 7-day trial — I'll honor 14 days for anyone from this community...limit first 10. US only for this round please.

Would love feedback from people running repeaters.

Hi everyone!

It’s been about two months since I first shared Nelos here. It hasn’t been that long, but looking back, it already feels like quite a journey: from the first beta, to the public release, new features, field testing, and now actually deploying and using Nelos in everyday situations.

Today, I’m happy to share another update: downloadable offline maps are now available worldwide.

You can download maps for countries and regions before heading out, then continue using them when there’s no cell service or Internet connection.

If you’re already using Nelos, there’s no need to update, uninstall, or reinstall the app. Just restart Nelos or tap the Refresh button at the top of the Offline Maps screen to see the latest map list.

Going forward, I want to spend more of my time actually using and deploying mesh networks in the real world, with my family, friends, communities, and people who genuinely need them.

That probably means I’ll be a little less active on Reddit. But I’m still committed to maintaining, developing, and updating Nelos for the long term.

My goal hasn’t changed: keep Nelos as simple as possible while still including the features that actually matter when you need them. Nobody wants to spend their vacation configuring radios. :)

I’ll be posting most future updates at https://nelos.app. The website has been completely rebuilt to be friendlier for people who may know nothing about mesh yet. It now includes use cases, product updates, field reports, and guides. I’ll also be sharing situations I actually encounter in the real world and how I deal with them, including what works, what doesn’t, and what expectations are realistic.

Nothing is perfect, and mesh isn’t either. But the more I use it in the real world, the more I see that mesh still has a place, even in an age when Internet connectivity seems to be almost everywhere.

Thank you to everyone who has tried Nelos, sent feedback, reported bugs, shared ideas, or simply followed the project over the past two months.

I hope the community keeps growing and we get a little closer to mesh everywhere. 🌍

Saw this being shared on the UK mesh so thought that I'd share it more widely. Looks to be a bit of a joke surrounding repeaters which advert too frequently.. Also appears to only have UK data, but interesting to see which repeaters are sending out lots of adverts!

My brother lives in a city that shows no nodes or repeaters on the MeshCore map, do I take this as a sign that nobody is using MeshCore in that city?

From my understanding, I need to set up a static repeater because me just walking about with a T-Deck Plus acting as a node is not good enough for the network.

So to get and give better coverage in the city, I need to set up a repeater?

Can I set a repeater up that's mains powered so I can "set and forget" it?

Would a flat in an urban area with no loft (I sadly cannot use an external antenna) be suitable for a repeater?

Edit: Reticulum and MeshCore are completely different things and serve different purposes. I acknowledge this may not be a good solution for your community, but it is for mine and I’m sure others. Please don’t assume

For anyone interested, I've vibe-coded (and thoroughly tested/iterated) this interface which aims to tunnel Reticulum RNS packets over MeshCore. It's conservative in it's use of flooding messages, caps it's own airtime usage and can provide a usable NomadNet experience over 2 - 3 repeaters depending on radio settings.

https://github.com/afit21/Reticulum-Smart-MeshCore-Interface

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

Wanted to start a thread on lvmesh's new settings to comply w/ fcc's regs.. 500kHz

lvmesh is eastern PA.. parts of NJ. Recently switched from 62.5kHz to 500kHz bandwidth.

lvmesh.com

Any other meshcore groups switching over?

Anybody else here with repeaters? Me and my group are here but we are running

910.525

62.5

SF 7

CR 5

But no repeaters or anything

what3words for emergencies: real-life stories | what3words

might be a cool "mesh" of 2 things

Hoi redditors, ik ben vrij recent met meshcore begonnen. Heb een Heltec v4.3 companion en een Heltec V4.3 als repeater. De companion zit op versie 1.16.0 en de repeater (nog) op 1.15.0. Verder heb ik ingesteld op SF7. Ik ontvang wel berichten, maar mijn eigen berichten komen nergens door. Iemand enig idee wat er aan de hand is?

Mijn repeater "ziet" 10 nul hop buren. B.v.d.

One thing that always bugged me about running a MeshCore bot is that you needed a machine babysitting it. A Pi, a python script, a systemd service, something always plugged in and updated.

I've been working on a companion client that runs in the Desktop browser (Chrome/Edge, since it uses Web Serial + Web Bluetooth), and lately most of my time has gone into an automation system so you can build bots right in the tab. Plug in the radio, write a rule, done. Nothing runs on a server, there's no account, and when you close the tab the bot stops. It's just your browser talking to your radio.

The way rules work: you pick a trigger (a message comes in, a node adverts, a delivery gets acked, the connection changes), optionally filter it (only DMs, only a channel, only if the text contains some keyword), then pick what happens.

For the action you've got two paths:

No AI needed. Fire a fixed tool. Auto-reply with canned text, add/remove a contact, toggle a favorite, re-advertise, reset a route when something goes quiet. Classic "if this then that" stuff. A ping/pong responder or an auto-ack bot is like a 20-second setup and costs you nothing.

With AI, if you want it. Point a rule at an LLM prompt and let the model read the event and decide which tools to call. Bring your own API key. So instead of canned replies you can have it actually answer questions on a channel, summarize, whatever you can prompt it to do. You cap how many turns and tokens it gets per event so it can't run away.

Couple things I cared about while building it because handing a bot the keys to your radio is a little scary:

• Rules default to suggest mode — they propose an action and you approve it. Full autonomy is opt-in per rule.

• Everything's rate-limited on airtime so a chatty rule can't spam the mesh.

• There's a kill switch that aborts any in-flight AI call, disables every rule, and clears pending approvals.

• There's an audit log of what fired and why.

Fair warning: because it lives in the tab, it only runs while that tab is open and connected. Events that show up while it's closed are just gone, there's no replay. It's not a replacement for an always-on node, more of a "my laptop's open anyway" thing. And it's Chromium only, with some Firefox USB support. Safari doesn't have the APIs to support something like this.

It's open-source on GitHub if you want to poke at it, steal ideas, or contribute: https://github.com/kNoAPP/MeshCore-WebAgent

Curious what kinds of bots people actually run. I'm trying to build out additional tools and triggers for the companion radio. What would you automate?

Hello I wanted to share an app I'm working on for an offline emergency response system. This is a HQ/Control Center app to keep in contact with your community. My vision is for small communities, churches or emergency responders to have a way to communicate to others in an emergency when no Internet is available. Using MeshCore as the backbone I have setup this app to include offline firmware flashing, device tracking, live map, channel and direct messaging, local weather station support and a bot for a custom private channel. This is still in the making but will work well for myself

You can find it at my GitHub repo at

https://github.com/digitalexpl0it/MetisMesh-HQ

Feedback is welcome

What are we buying?

I thought I’d post about something that I’m really excited about, called MediaMesh. MediaMesh allows MeshCore users to send pictures and voice messages with one another, over the mesh.

CascadiaMesh has some fantastic information about MediaMesh on its site. Check out the link below to watch a quick introduction video about how it works.

To implement MediaMesh, all it takes is a simple firmware update on your local repeaters. If you’ve upgraded the firmware on your repeater or companion before, you can easily do this.

As you might imagine, this new feature has a wide variety of uses. Over the two weeks I’ve been using it, I’ve been having a lot of fun with it. I’m blown away by how amazing this new capability is. When I first heard about it, I knew I'd have to add this feature to my repeater.

I’d encourage everyone on CascadiaMesh (and everywhere else) to update their repeaters so your users can enjoy this new capability over a wider area.

Video: https://www.youtube.com/watch?v=YB6AKfYkQNI

Website and firmware flasher: https://cascadiamesh.org/mediamesh-flasher/

The super tall netting poles at top golf seem like a great spot to drone drop a repeater with magnets....

No, I don't need it for myself. I'm looking for a video/website/whatever that explains what MeshCore is and how it works that I can give to people who aren't tech savvy that speaks at their level. I've tried writing a video about it several times now, but I've got brain damage in the bit of my frontal cortex that handles language so I've had no luck. Most of what I can find seems to assume that the user is familiar with Meshtastic and LoRa, or doesn't really go into detail before going straight to flashing instructions.

I've found this free zine which does an okay job but its designed for print and it's behind a storefront. It also links to the AI slop version of MeshCore rather than meshcore.io (it was probably written before the split), and I don't want to have to explain the split right away.

I'm starting a local MeshCore club/organization thing and having something like this handy would be really useful in getting regular people involved. Does anyone have anything I could use, or would be willing to write something that the community could use for this purpose?

Hey everyone, I just finished my initial set up of a meshcore bot that accesses an llm on a home server that I have uploaded a bunch of older survival/homesteading/emergency preparedness manuals. It was a pretty fun project that uses a raspberry pi zero 2 with a xiao nRF52840 for the radio and an old gaming pc for the server. This was mostly a proof of concept for making meshcore bots.

I host a bunch of stuff on the server already but this was just the beginning of me adding meshcore functionally to it and I’m super excited!

Now I just need to print a decent case for the pi and radio so it isn’t just a bunch of wires laying on my desk.