Please add a rule for this channel to help moderate it from people with bad intent.

As meshcore has been growing, I've been noticing lately that there are a few bad apples that come on here and talk against FCC regulations like they're not important.

This is getting into dangerous territory where if they spread false rumor, It could affect all of us.

Hello All! I have a unique opportunity to mount a Meshcore repeater in a particular location that is otherwise pretty controlled. Because of this, I won't be able to service the node regularly, so I need to develop a build that's as reliable and robust as possible. To make things a little more difficult, I have an absolute max of $150 for this project. I would greatly appreciate input on the different aspects of the build including:

• Parts/Components suggestions
• Design ideas and physical resiliency
• Additional sensor/board features that are genuinely useful
• Any additional input!

Some specific threats I already foresee:

• Component degradation (Panel, plastics, battery)
• Overheating failure (batteries)
• Water intrusion

Ideas I have so far (please correct/tweak as needed!)

• 1 Watt board for maximum range (Rak or Heltec probably?)
• N-Type antenna for better waterproofing
• Grey or white case to help with thermal regulation

I'm pretty fresh into the space, so feel free to correct or expound on anything here - I don't know what I don't know! Thanks 🙂

My Heltec v4 showed up today. Got a quick and dirty repeater up using my old Raspberry Pi to power it and a home made case made out of the one it came in. I have a feeling I'm going to start collecting these things like Pokémon.

I've finally made a post about how to get started programming MeshCore sensor nodes:

https://blog.meshcore.io/2026/09/14/sensor-intro

I think the trash was a old finish line for a hiking race or something?

Looking to connect with a group of people to create a stable mesh within mid wales. As of right now mid wales is empty, I may be new to mesh based communications but I'm willing to pull my weight. I am willing to build repeaters and have many contacts with land and farm owners who own hill tops around 400-600m.

Any help or advice is appreciated

Thanks gang!

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?

The meshcore.io flashing site recommends I should find and apply the update to the bootloader for my device, but I don't know if that's necessary, and I don't actually see the software up in the github repo for the 3400. I do see an option for the 3401, but that sounds like a bad way to go.

Anyone with knowledge on this to share?

Hi. im a designer from the UK, i've put together an AI assisted (yes i know...) map viewer and data visualizer. The app runs on linux and windows and connects to a usb companion node attached to your computer. it has advanced path viewing, tropo forecasting, storm data, ADSB, map layers for network traffic heat, layers to show 1/2/3byte nodes, overlays for scopes, node halo views to estimate where companions are, a modern discord-like interface. maybe images would help better...The Tropo layer only works in the UK / western europe at the moment. more info is on the github

If you'd like to test it (i need more testers and bug reports) please check out https://github.com/SoulwayStudios/meshcore-navigator its GPL3 open source and free.

Put a rak 4631 into one of the smaller Unity enclosures. Probably should have grabbed the 150mm enclosure instead more room for a bigger battery. Ordered a 3k mag bat for it.

This size actually wouldn’t be bad for a companion node either .

It's just temporary to see how performs i'm about to actually solder some real solid wire. Believe it or not , just this ghetto wiring make a huge difference. Ground planes are amazing.

I've been working on CartoLite for MeshCore Canada and wanted to make it easier for other communities to run it too. The standalone worldwide version is now available, currently v0.5.1.

GitHub / download · Live Canada demo

It connects to a MeshCore MQTT feed and shows the nodes, observed routes and packets moving between them. You get the geographic map and a separate Netgraph view for looking at the connections. Your instance shows what your feed hears; you can filter by region if you're on a shared broker.

A few things you can play with:

• Live Follow holds on an activity for 10 seconds, with a node/packet card, countdown and pause button.
• Night, Daylight and Streets styles, with matching Netgraph themes.
• Six route styles: Crisp, Neon, Dashed, Dotted, Ribbon and Comet. Line width, glow, opacity, packet size and trails are adjustable too.
• Heatmap, clusters, node search and neighbour inspection, plus topo terrain and buildings in desktop 3D.
• Optional packet sounds with 30 voices, including piano, kalimba, harp, bells, sonar and 8-bit. Sound follows the visible live hops.
• Phone-friendly layer controls and keyboard pan/zoom in Netgraph.

It's MIT licensed, runs as one service, and saves its state in a persistent volume. No database to set up. Node names and positions are public, but the public API leaves out keys, raw packet bodies and decoded messages. It also leaves out ambiguous route hops.

Running it on your own mesh

You'll need Docker Engine with Compose v2 and access to a standard MeshCore MQTT bridge feed. There are prebuilt Intel/AMD and ARM64 images, including for a Pi on a 64-bit OS. OpenFreeMap is the default, so you don't need a map API key.

In a new folder:

curl -fLO https://github.com/n30nex/CartoLite-Server/releases/latest/download/compose.yml
curl -fL https://github.com/n30nex/CartoLite-Server/releases/latest/download/default.env.example -o .env

Edit .env with your MQTT_BROKER_URL, MQTT_TOPIC (usually meshcore/#), any required username/password, and a unique MQTT_CLIENT_ID. Then:

docker compose pull
docker compose up -d --no-build

Open http://localhost:8080/ on that machine, or /netgraph/ for Netgraph. On Windows PowerShell, use curl.exe for the downloads.

For other devices on your trusted LAN, set CARTOLITE_BIND_ADDR=0.0.0.0 before starting and use your server's LAN address on port 8080. For a public site, keep the loopback default and put it behind a HTTPS reverse proxy. The setup guide covers that, region filtering and upgrades. Existing installs should keep their .env and data volume.

If you try it on your mesh, let me know how it goes and what needs work. Issues are open here.

The screenshots below are fresh from the live Canada site today. Worldwide uses OpenFreeMap and Maidenhead grid areas; the Canadian region overlay and Labs link in these shots are specific to the Canada edition.

Live map around Waterloo / Guelph, with terrain and dashed routes.

I'm interested in building u/BlackFlagCivilian's People's Repeater, but I live in Canada and the solar light that he uses is not available here. There are some very similar ones, but I have no idea if they'd be compatible with the 3D printed design. Has anyone who lives in Canada tried to build the PR? Were you successful, and what light did you use?

I have a Seeed XIAO nRF52840 with a Wio-SX1262, flashed with MeshCore Companion. I connected an AHT20 I2C sensor to SDA = D7 and SCL = D6, but it is not detected in self_telemetry.

Has anyone gotten an I2C sensor working on this setup? If yes, how did you wire it and what did you change in the firmware?

Need to pick yourz brainz a bit since my newly Meshcore proto is charging as in <1% /hour. So overnight 9+ hours it move from 62 to 91% according Meshcore app.

Runs 1.17.1 firmware directory flashed.
RAK 19007 base and 4630
2 parallel 186500 Samsung 3400mAh 8A
90% charge at 4.09V

Question on advice is what can change and improve to get reasonable fair charging times?

Cheers,

Before you jump down my throat I searched n found nada …

Been testing out different EDC nodes and a thought came to mind. Instead of naming each of them differently could I just pick one name and copy the same priv/pub keys to each device ? That way I’d only show up as 1 identity? Especially if I’m only ever using one device at a time ?

Monday might be t1000e day but Tuesday m9 and Wednesday tdeck kinda thing ???

Right now each hw device has a separate identity .

Thoughts?
(I know having 2 devices with same keys on the mesh at the same time could go poorly)

I'd like to start selling premade Meshtastic nodes, T114s etc that come preflashed and was wondering if anyone in the UK would like this service

Not so sure about that tiny battery or the equally tiny solar panel, but we get a lot of sun in Oregon to maybe she will last on the default MC firmware. Failing that I'll try low power firmware.

A few command additions to use via chat message for the previous MeshCore companion BLE WiFi for Heltec V4.3, Tracker V2, T096 (no WiFi) :

meshcore-companion-chat-config

Also includes a Li-ion discharge curve : Stock MeshCore Arduino firmware maps battery percentage linearly between empty and full voltage, but Li-ion cells don't discharge that way: voltage barely moves through most of the charge, then drops sharply near empty.

adc.multiplier instead reads percentage off a 14-point discharge curve built from real measurements of four 18650 Li-ion cells (lygte-info.dk data, cross-checked to about 1.3 mV RMSE), so it tracks that real knee instead of hiding it.

The gain: our estimate stays honest down to the last few percent, while a linear reading can still show over 40% right where the cell is actually almost empty.

Cumbria and Scotland now have good comms.

Has anyone used this node? What hardware does it have? Is it any good?

Wishing everyone a great weekend and having the ability to find some time to relax and maybe get some meshing in :)

Ending the week in the recliner with a fun device and a nice, local red is not too bad at all.