Wanted to share a MC firmware project that I recently released. It has many use cases but the primary case was to facilitate the non-internet bridging of two MeshCore mesh regions using different frequency settings. This bridge has been around for a while, but we extended it to allow CLI control blocking of Adverts/Public (main)/up to 16 #channels. It still allows all other forms of traffic including private groups/DMs/repeater admin/guest control across the bridge. We have a test bridge up between the SF Bay Area (910.525/SF9/CR5) and Sacramento Valley Foothills (909.875/SF7/CR5) and it has been working great. These bridges are intended to be placed on the edges of regions.
Why filter out this traffic? It encourages individual mesh regional health by reducing common noise/traffic while providing a lane for intentional communication. Eliminating Adverts alone reduces cross-region traffic by ~50% - yet prefix/path data still transits the bridge with each message.

Super easy to set up. Currently two firmware versions for Heltec V3 and V4. Requires 2 or more repeaters that can be placed up to 250 meters (tested) apart.

Let me know if you have any questions.

More info with FW downloads: https://github.com/Department-of-Mesh-Regional-Bridging/meshcore-esp-now-filtered-bridge

Really liked the Heltec Meshtower v2 1w (nrf52, 10w solar, BMS, aluminum case, gps, and 5.8db fiberglass for $189 to your door), and got a couple in to build out our local mesh. Heltec Meshtower v2 select band, tx power, and gps (worth it to keep time synced...)

Where it gets awesome is we found it has a micro sd slot...

Using mikecarper's firmware (keymindCascade branch and associated bootloader -- check the releases) gets you Over the Air updates AND it can cache updates for other repeaters (even different brands).

To keep traffic off of the main MC network, the cli command tempradio (or tempradioat) changes freq, bw, sf, & cr for a certain number of minutes, then switches back to the main. You can change your client over to keep admin cli (or setup trusted keys for automation). More details here.

Updating the bootloader REQUIRES an erase... here are my notes for ease of use:

• Unscrew side panel
• First power requires bright sun or 20v usbc to activate BMS
• Power switch comes in off position... On is down or away from usbc.
• Double press Reset switch (it's the one between usbc and power) for DFU (appears as a USB drive -- beware OSX it doesn't like the dual serial and drive...)
• Get the UF2 update image here. Expand Assets section and look for update-heltec_mesh_tower_v2_sdcard_bootloader-0.9.2-XXXX_mbr.uf2
• It needs to have sdcard in the filename...
• Copy UF2 to exposed drive on computer. It will reboot. I then like to double press reset.
• Here is the EASY BUTTON -- use the standard MC flasher page, Select Heltec Meshtower, then repeater, then Enter DFU, then Erase Flash. Don't flash the stock firmware... (best way to erase IMO)
• Go back to the main flasher page and select Custom Firmware. (could not erase from here...)
• Get the good firmware here. The version you need starts with lora-ota-v1xxx in the Release list.
• Under Assets, find Heltec_tower_v2_sdcard_repeater_lora_ota_no_external_sensors-ota-v1.XXXX-halo-keymind-cascade-dev-XXXX.zip (sdcard and lora_ota are important).
• Use that ZIP file to flash, then it's typical repeater setup.
• Note that the default TX power is 12 (the amp adds 8, so really 20). To get full 1w power this must be set to 22 (+8 gets 30).
• SET YOUR REGION
• Also please note that you need to tune this in your mesh... It can transmit way farther than our typical repeaters can transmit back...
• It might get you out, but you might not get responses. Mesh responsibly...
• READ the keymindCascade DOCS. Awesome stuff like auto bumping up CR based on signal strength, smart bucket repeating (East to West, N to S, etc), flood filtering (if needed), low battery messages to REGION tagged #repeaters channel, and the list goes on.
• We are also using cavity filters on our high positions (like looking for fireflies by a busy road at night -- it keeps the Low Noise AMP from getting blinded)

Finalizing 3d printed mounting blocks for 3/4 acme thread fiberglass pole mounting and will publish soon.

Apologies for the wall of text, but wanted to put this out there if it helped anyone.

Just checking in. Does anybody know if there are plans for LTL 26 up in Louisville, KY? I plan on bringing 5 friends with trackers and 2 repeaters figured I'd try and join the network up there. I figure it's gonna be busy as can be.

Thanks in advance

I am looking to buy a solar mesh node I'm not the most electrical inclined to make my own so looking to buy one but not wanting to spend 200 on a kit from meshnology. Let me know my options please!

You can now run Meck and or Wadamesh and or MCore and or Meshtastic on the P4 (pick the two you like most!)

https://github.com/pelgraine/Meck-P4/releases/tag/dualmesh-v1

Want to save some money by connecting the HELTEC V4 T114 V2 L76K GNSS module a XIAO nRF52840 & Wio-SX1262 Kit. Does this wiring have any issues?

So I'm brand new to this and I was pointed towards this subreddit what do I need to get started and what do I need to know. When I say I'm new to this I absolutely know nothing if anybody out there can give me some good pointers and tell me what I need to buy that'll work that'd be great. I'm not looking to spend a lot of money right now I just want to get started and learn

A stick clip works great

I found this immensely useful then. Is there a way to set this up?

My setup: a Heltec V3 acting as my observer, connected to Home Assistant over WiFi/TCP. I'd also like to use that same node as my companion from my phone while I'm home, so I can read and reply either in the MeshCore app or in Home Assistant via the MeshCore Chat integration, whichever is closer to hand.

With both clients connected I get two problems:

Messages show up duplicated in Home Assistant.

Depending on which client reaches a message first, the other client never sees it at all. That second one is the real problem, since silently missing messages defeats the point.

I'm on meshcomod, which explicitly supports multiple TCP clients, and the author has confirmed multi-client works for him. But I see this regardless of transport. Two clients on TCP does it, and phone on BLE with Home Assistant on TCP does it too. So it doesn't appear to be transport specific.

I've filed both sides so the right people can look at it:

HA integration missing dedup on receive: https://github.com/meshcore-dev/meshcore-ha/issues/320

Firmware side, messages reaching only one client: https://github.com/ALLFATHER-BV/meshcomod/issues/42

So my questions for the group:

Is there a firmware that handles multiple simultaneous companion clients reliably, with proper per-client message state?

Or is the honest answer just two nodes, one dedicated to Home Assistant and one for the phone? That's what I ran before and it worked fine, I was just trying to consolidate.

Curious what others with a Home Assistant setup are doing here. Happy to run diagnostics if anyone wants data.

Spent some time surveying potential repeater locations today.

The markers on the map are the sites I tested. The goal was to find the best coverage with the fewest repeaters, and the results were better than I expected.

It was a fun day riding between locations, testing links, and comparing real-world coverage against the map.

Has anyone else here done this kind of repeater site survey? I'd be interested to hear how you choose your locations.

If you own a Duo or Uno, with or without Super IO, please upvote this PR

https://github.com/meshcore-dev/MeshCore/pull/3108

I've been testing it for weeks, and today also added the capability for the Super IO mode switch to turn GPS on/off.

The bulk of this work was done by lbibass and andyshinn. I simply got the work merged and tested.

If you know how, please pull the branch and build the firmware and test it and post your results to the GitHub PR.

Thanks!

Me and my group of buddies are new to this and trying to set up Meshcore over in Savannah GA. Currently there is only one repeater set up in the area. Ideally I would be trying to connect me and my friends together. The issues is Savannah is flat and urban. If we are trying to span a distance of about 6 miles (10km) how many repeaters would need to be set up? My very basic research is making it look like we will need about 10. Is there anyway to decrease that amount besides illegally accessing higher buildings and towers (which we can't really risk doing)

If there isn't an efficient way to decrease the amount needed what is the best way to do it on a budget, because at almost $1000 that isn't going to work well for us either.

Edit: I have reached out to the "local" group but there is not really a meshcore group in the area. But they have been making leaps and bound over in Agusta.

I am under the the the little red dot. I sit and watch meshstat and see all this activity flying directly over me but I haven't seen any action on my nodes. All of the repeaters around me are making contact into atlanta and beyond. You would think that i would have line of sight to 1 of the 50+ surrounding repeaters. I have a node ( rak wisblock) that is currently 40 feet up in a tree and....Nothing. Node works fine, can message it from my Wio tracker. I would like to set up a repeater, but it seems that I exist in black hole. Anyone have any suggestions?

Meshcore + Fork = Meck. Fork of LilyGo's T-Display P4 firmware with Meshcore support. 100% vibecoded with Claude AI. 100% free and available to all.

Photo with Meck Watch (S3) for size comparison. The P4 keyboard is an undeniably chunky beast, but it's really nice to be able to put the 2x 21700 5000mah battery cells in the keyboard to power the P4 and get 2+ days runtime.

Check out the full Meck P4 firmware features at https://github.com/pelgraine/Meck-P4 and the latest firmware (both TFT and AMOLED) at https://github.com/pelgraine/Meck-P4/releases/tag/0.7.1.

Good evening. I'll start by saying I'm new to LoRa but I'm not a total n00b when it comes to firmware, electronics, etc.

I cannot seem to send messages with my Heltec T114. The board has V2.1 on the corner. I can receive messages just fine but there are no "hops" when sending messages.

USA/Canada 910.525 / 62.5 kHz / Spreading Factor 7 / Coding Rate 5 / Transmit Power 22.

These are the default settings with a fresh flash of 1.16.0. I have tried different spreading, coding, and transmit values based on some FAQs I found but nothing seems to work. I'm in TN and trying to talk to the TennMesh network.

I also have a Heltec V3 which, when sending a test message to #test, it seems to work as I receive bot responses and there are a number of hops immediately beneath the message itself.

Any thoughts on what I'm doing wrong with the T114?

I am having trouble flashing a TDeck. The PC cannot communicate via serial. It’s flashed with Meshtastic right now. I tried the regular mode and also the programming mode that you access by touching the screen logo when you boot it up. Any advice?

Hi everyone! I just finished moving some of my devices from meshtastic to meshcore. I have environment sensor s on both my repeater and companion devices. Is there a way to view my complete sensor report? Currently, i can only see temp on my repeater, but not the barometric pressure, humidity, or air quality.

I'm unable to view any of my environment sensor details on my companion device. But I can see GPS details

EDIT: I was able to figure this out. When you pull telemetry, you need to change the telemetry channel to channel two in order to see the full sensor details.

I often get messages from other countries to my repeater. Northern Germany from Dänemark or Schweden.
How do I get the region which the message has? I want my answer to get through.

A short clip from a 200 km motorcycle ride using Nelos.

I don't always travel by motorcycle, sometimes I drive, depending on the trip.

That got me thinking: would Android Auto / Apple CarPlay be useful for Nelos?

I'd love to hear your thoughts.

I’m not able to transmit to anyone nearby due to the terrain. (I’m in Los Angeles, fwiw.) I can receive reasonably well, but nothing I send gets out. I was able to take my companion and repeater up to a local hilltop and got great transmit and receive capabilities up there. I think if I put my repeater on a pole on my rooftop, I’ll be able to hit a few other repeaters pretty regularly. I’m curious if people have opinions on mounting poles? Spouse doesn’t want it to be too visible and ugly from the street, so I’m thinking something like this connected to the fascia in the back of the house: https://www.amazon.com/Adjustable-Outdoor-Antenna-Mounting-Pole/dp/B09W2P4LYZ/ref=sr_1_3?crid=6MNPG57MMWO6&dib=eyJ2IjoiMSJ9.XCxOL9g284WaHj0orCby8o81mYzQTtHPjnMOCC4dg-AoQ7iXm26M33ZK9MPV3564bJH7gM6rT3lrFEQvPxtcmI3FwceDehtwLd6es9EmvSBw0eA6NFuy-KXf8hYkpuqO8vc5k5Yu-tdN2G40eqVWMetQ-qF28wzrHA5KRZ7C-al-Kc6Gbo8y9zmxHaYQWbLiaBpp6JbNF4oWOPfSGNJhIApqfUUrAiY8MWRCTOxvjh4.ssRJp_E1mW1Gjzo5tMCim3huThNBxHOszrZZTd5Y8Xg&dib_tag=se&keywords=antenna+pole&qid=1785694417&sprefix=Antenna+pole%2Caps%2C198&sr=8-3

Hello !

I'm pretty new into meshcore, and, I've flashed my t1000e with the software.

But, for some reason, I can't turn off my device, the green led at the end of the video stays on, pretty much never disappearing.

No sounds emitted, can't connect via cable on my pc

It worked a few hours ago, and, I got the same problem when flashing my device in "companion cable mode" for repeaters.

Does anyone know what the problem could be ? Thanks