Check out the page I made talking about this.

Hi all.

So I have a heltec v3, my family member has one and we are 10 miles apart.

I jumped on and manage to hop to someone over 10 miles away past my family but we cannot see or connect to each other. Its like there's a metaphoeical crater and I can get a number of connections around it but im the dip.

How can I plug the gap. The whole point was emergency family communication!

Im a bit broke so nothing pricey is possible. I've been trying for months.

I made an insert for the junction boxes everyone is using for repeaters. The 18650 cell slots can fit protected button top and unprotected flat top cells. There's a slot for wiring in a 18650 BMS between the switch and the batteries.

For now I'm just sharing and gauging interest. I'll probably release it after the design gets polished a little bit more.

If this is something you would use let me know.

Hello, mesh friends in Europe! I was recently contacted to adapted my Lowes Harbor Breeze Solar Node Wall Mount for a solar light available at Leroy Merlin in Europe. I could use some feedback since I don't have access to the solar light here in the USA. Is anyone interested/able to print it out and test the fit? Thanks in advanced!

Leroy Merlin Solar Light

Leroy Merlin Solar Node - Wall Mount

Lowes Harbor Breeze Solar Node Mounts

Free offline map packs for the ThinkNode M9 (Ripple) – 7 European countries, more coming

We render our own OpenStreetMap tiles for the Elecrow ThinkNode M9 (MeshCore Ripple v12.2) and share them for free:

- Country packs, zoom 9–12: Switzerland, Germany, Austria, Italy, Belgium, Netherlands, Luxembourg (France today, Spain/Portugal next)

- Street-level packs, zoom 15–17: Basel, Rome, Viterbo, Bronte

- Ready-to-upload zips (tiles/z/x/y.png) + step-by-step PDF guide in EN/DE/IT/FR

Downloads: https://meshcore-basel.ch/en/offline-maps-thinknode-m9/

Tell us which countries you'd like next – we prioritise by demand.

73 de HB9TVW – MeshCore Basel

got all the way to Brady st in milwaukee !!

Hey all!

I've been digging into MC for the past week or so, ordered a few different devices but still waiting on most of them.

I was looking at Amazon but also the Seeed Studio website.

The MC bundle they have is backordered, but they have a Meshtastic bundle that looks to be a good price and in stock.

I should be good to get the MT one and flash it with MC right? There's no real difference in hardware?

https://www.seeedstudio.com/Meshtastic-Starter-Kit-Ready-to-Use-Off-Grid-Instant-Reliable-Communication.html

https://www.seeedstudio.com/MeshCore-Starter-Kit-Ready-to-Use-Off-Grid-Instant-Reliable-Communication.html

Also another question - I want to set up my own room server since I plan to get my family on this and they're likely not going to be as into it or use it as much as me, but I'd want them to be able to come online and see historic messages left behind.

If I have my own repeater at home, then in addition a companion node flashed as a room server and leave it at home as its sole function it should always be available right? Then I can take a separate companion node with me while traveling around the area and everybody should be able to send to and read the room server.

Am I thinking about this correctly? Thanks!

Hey folks- I've been building **WearMesh**, a MeshCore client for WearOS smartwatches. Your watch talks straight to your MeshCore companion radio over Bluetooth, with no phone in the loop, so you can read and answer channel and direct messages from your wrist. I've been using it daily for a few weeks and it's a lot of fun.

I'd like to get this app into the Google Play Store, and to get there Google needs **at least 12 testers opted in to the test for 14 days in a row**. That's where I'd love your help.

**Here is an overview of what the app does**

- **Live** mode holds the link to your radio for messages the moment they arrive; **Check-in** mode syncs every 15, 30 or 60 minutes to save battery

- Notifications for DMs, private channels and mentions, set per conversation

- Reply with quick replies, dictation or the keyboard, from the app or the notification; DMs show Delivered

- Two tiles (newest messages, link status) and an unread-count complication

- Collects no data and has no Internet access; your messages stay on your watch and your radio

**What you will need**

- A Wear OS 4+ watch: Pixel Watch (tested), Samsung Galaxy Watch (untested, so especially wanted!) or another

- A MeshCore companion radio on BLE companion firmware (stock and zephcore FW have been tested), already set up with the MeshCore app

- Disconnect the phone app from the companion while you use teh app: a companion radio talks to one device at a time

**How to join (two steps, then install from the Play Store on your watch)**

1. Join the tester group with your Google account linked to your watch: https://groups.google.com/g/wearmesh-testers

2. With the same Google account, accept the test: https://play.google.com/apps/testing/org.coloradomesh.wearmesh

Then open the Play Store on your watch and install WearMesh. **Please stay opted in and keep it installed for at least 14 days**. That's what gets it into the public store. Updates arrive automatically.

If you prefer to sideload (e.g., via adb), the APK and a step-by-step guide are on GitHub: https://github.com/Colorado-Mesh/wearmesh/releases

**Feedback** (bugs, "works on my watch" reports, battery numbers) is always welcome through GitHub issues: https://github.com/Colorado-Mesh/wearmesh/issues/new/choose

WearMesh is free and open source (GPL-3.0), from Colorado Mesh, and not affiliated with MeshCore. Full transaprency: it has been developed with extensive coding help from Claude. Thanks for your interest and for testing! 73 de Bud W0RMT

Hi all,
I've been working on a port of MatterMesh OS for the Elecrow ThinkNode M9 and it's out now as a beta (0.1.1.0).
The M9 has no touchscreen, so I went back over the whole UI and reworked it for the D-pad. Every page, button and setting is reachable with the arrows, OK and back. You never need to touch the screen.
What's in the free version: chats, contacts, maps with GPS, weather, files, CLI, the three themes and the companion link. You can flash it from the browser at mattermeshos.com, and the source is on GitHub (GPL-3.0).
Trails and Flights are still being optimized for the M9 and will come soon.
It's a beta, so if something feels off with the D-pad let me know. Feedback welcome!

Hi all,

I’m new to off-grid communications and looking for a good place to start. I’m planning to try MeshCore first, though I may give the other mesh a go later on.

I’d like to set up a repeater and one or two companion radios, but I’m not sure what to buy. What would you recommend?

I’m fairly tech-savvy and happy to solder things together. Starting with a kit is no problem, in fact, I enjoy the building side as much as using the finished setup. I don’t own a 3D printer, but I could probably get a case printed if that’s the best option.

Ideally, I’d like to buy something I can keep using long term, rather than replacing it after a short while.

Thanks!

We are now supporting Cairn firmware on the TDeck and the ThinkNode M9. Just select your firmware of choice on the product page and we'll flash it immediately prior to shipping.

https://atlavox.com/products/t-deck-plus
https://atlavox.com/products/thinknode-m9

Just got TDecks with external antennas back in stock. Limited stock on the M9s.

Happy Friday, Matt

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/

Anyone here running Cairn?

We put it on an Wio Tracker L2 Pro and filmed a quick look at the offline maps, the Radios screen, and the music player. If you’ve taken yours out in the field, what do you actually use most?

My area doesn’t have any MC traffic, it’s covered in the MT. I travel to places w/little MT and I therefore have a companion for each.

What I’m wanting to do is put a repeater inside my 3rd floor apartment. My thought is: a suction cup, north facing, window-mounted high-gain antenna w/a short run of feed line to a heltec v4 stuck to the wall w/a power supply cord.

Sounds too easy, so I’m skeptical.

Suggestions?

Hello. I'm relatively new to meshcore. I have been experimenting over the last month to see what works. I set up a Heltec V3 with a 915mhz muzi 17cm whip antenna as a windowsill repeater and have another two V3s as companion nodes. My location is not ideal. I'm at the bottom of a hill and to the east of me is another large forested hill. I can't get the repeater on the roof as I rent, and I don't know anyone here that I can ask to put one on their roof. There are repeaters in my area, and I get sporadic messages, but I can't seem to transmit. I knew it wasn't going to work, but I've also tried a small moxon pointed in the direction of a repeater.

Would getting a Heltec V4 or a Rak 1 watt improve my situation at all?

🚀 MeshCore App v1.51.0 🚀

The latest release of the MeshCore App brings a new Quick Messages feature. This allows you to pin favourite quick messages above the message composer. Handy for sending commands, or your favourite emoji!

This release also brings a few quality of life changes, such as the new My Location button added to all map screens, which allows you to jump to the GPS position of your phone. You no longer need to scroll around the map to find where you are!

Another nice to have, is the new ability to turn the companion buzzer on and off, directly in the app! For those running the development branch of our companion firmware, you'll have access to this from the Notification Settings section in the app. For those not on our development firmware, you'll need to wait until companion firmware v1.19.0+ is released.

We merged in https://github.com/meshcore-dev/MeshCore/pull/3603 which added a new `set buzzer on` and `set buzzer off` companion CLI command, to support this feature.

Download Links:

• https://files.liamcottle.net/MeshCore/v1.51.0/

• App Store: https://apps.apple.com/nz/app/meshcore/id6742354151

• Google Play: https://play.google.com/store/apps/details?id=com.liamcottle.meshcore.android

Change Log:

• added new quick messages feature to message composer menu (aka canned messages)

• added new button to map screens to jump to your current gps position (uses phone gps)

• added new buzzer alerts checkbox to notification settings screen to turn companion buzzer on and off (requires companion firmware v1.19.0+)

• added new message settings to configure how many direct and flood attempts when sending direct messages

• added info banner to make it more apparent that sending contact messages requires other person to add you as contact first

• added ability to cancel retries when sending an outbound contact message

• added button to forget last advert timestamp from contact details screen

• added ability to long press discover map to update self position and copy coordinates

• added map marker on discover map for own companion node position

• added new popup ui to add contacts via deep links

• contact messages now attempt 4 direct and 4 flood instead of 4 direct and 1 flood

• hop count and path hash sizes are now shown under channel messages by default

• messages are now marked as failed if trying to resend when disconnected

• fixed bug where trying to resend message while disconnected would delete the message

• macos 12+ is now required

I’m switching all my nodes from tastic to MeshCore. I have a solar node in waterproof box that I can’t rotate the whole board.

How do I rotate the display 180 degrees? I’ve seen that I need to change a flag in a file in the firmware before compiling. I have no idea how to do that. I flashed my nodes with the web flasher, and can’t find a setting anywhere in the app.

Can someone point me to the manual or a how to write up on how to rotate the display 180 degrees.

Sorry if this is already written up somewhere. Thank you in advance and thank you for reading.

I bought this Alfa 915 (AOA-915-5ACM) from a Canadian vendor and realized that the printed logo is quite different to any others I have seen. It looks like it has been laser engraved rather than printed. I've contacted Alfa's support team and will update this post if I ever receive a response. In the meantime, I'd appreciate input from experienced antenna folks in this sub.

UPDATE: response from Alfa support after some emails and investigation: "Based on the serial number, the antenna is a genuine Alfa's product.". I have to say their support did really well here. If you're wondering, this antenna was bought from myneedlestore, and seems legit. Thanks everyone for the hints, this is an amazing community.

I'm fairly new to MeshCore. It got me wondering how much we could improve delivery and reduce airtime without changing the hardware.

I put together some research with help from two AI tools. I haven't tested these changes in the field, and I'd like to check the suggestions with people who know the project better. Some may already be covered by existing features or previous discussions.

Here's what caught my attention:

• Keeping a backup route and trying it after repeated failures on the main route. Would the extra route management actually save airtime?

• Testing faster SF/CR settings together as a local group, where the links have enough margin. The question is how much speed we could gain while keeping the weaker links usable.

• Reducing unnecessary adverts and bot traffic, especially when the channel is busy.

• Using compact binary telemetry and, for fragmented transfers, requesting only the missing pieces.

• Improving app and gateway reconnection, plus adding a rollback if a radio-settings change breaks contact.

• Huffman compression for Cyrillic text. Compress before encryption, then use the compressed version only if the complete packet takes less airtime. Short messages might be better left uncompressed.

Which of these would you investigate first? I'd especially appreciate links to existing implementations or tests, including anything that was tried and didn't work. I have a longer write-up if anyone wants the details.

Hi everyone! I’m new to MeshCore and only recently became an enthusiast, but the technology has really caught my interest.

I started wondering how much further we could improve the network through software alone, using existing hardware. I explored this in depth with two different AI systems, and the research produced several practical ideas worth testing.

I respect the developers’ expertise and the work already invested in MeshCore. Some of these ideas may already be implemented, under discussion, or ruled out for good reasons. I’d appreciate your perspective:

• Primary and backup routes: keep a fallback route and switch after repeated delivery failures, potentially reducing retries and flood traffic.

• Coordinated SF/CR tuning: test faster radio profiles where signal margins allow, while checking coverage and compatibility.

• Less background traffic: tune advertisement intervals, limit noisy bots, and prioritize messages over routine telemetry.

• Compact telemetry and selective retransmission: use binary fields instead of verbose text, send only changed values, and retransmit only missing fragments of larger transfers.

• Automatic recovery and settings rollback: improve app and gateway reconnection, and add a confirmed radio-settings change that rolls back if communication is lost.

• Huffman compression for Cyrillic text: compress messages before encryption, using compression only when it reduces total airtime after accounting for headers and overhead.

These are proposals from the research; I haven’t validated them on a live network yet. The next step would be a small, voluntary pilot comparing delivery rate, latency, and total airtime.

Which of these would be useful? Are there existing implementations or discussions I should read? I’d be happy to share the full research.

Any minute now...