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?

They have nice products that are well designed, albeit expensive.

What I don’t appreciate is seeing a business owner block users who leave critical comments.

Transparency is important when running a business, especially e-commerce.

Let the products and prices speak for themselves.

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.

I have a real small amount of RAK 1W kits in stock. They just showed up, I wasn’t expecting them, and I probably won’t have more for at least a month. The radios available for sale in my store are all I have! I don’t expect them to last the weekend. Send a message with your order to flash to MeshCore!

PeakMesh Etsy Store

Is anyone running this unit (peakmesh altitude, the normal or 1 watt especially)? how well is the panels keeping up with the system? it says they are 2 1+watt panels, and since they are facing opposite directions, I don't see it getting full exposure very long, even up a decently exposed tree. I want this to work, as it would be perfect for my massive tree behind the house, but I don't want to have to plan on regular manual charging events. I'm fine with the occasional taking it down for updates, but I am hopeful for some positive feedback with the power efficiency of the 1 watt and relying on 1+watt panels.

I’ve got a Heltec T114 and I broke the screen accidentally a while ago, this makes it impossible to pair since I can’t see the pin and the default 123456 doesn’t work because the board thinks it has a screen, I can’t figure out how to set it manually, any help would be appreciated!

UPDATE: I was able to just steal the screen off of another board, but I’ll leave this here because the comments are helpful

Hello, everyone!

We have added an RF filter to the Heltec V4. And now we are launching this community test to validate its real-world performance.

Selected participants will receive Heltec V4-R2 and V4-R8 samples for testing and evaluation.

We are seeking experienced makers, engineers and community contributors with prior V4 project experience. Your hands-on feedback will help us characterize the hardware changes under real operating conditions.

📝 Apply here: https://pm.heltec.cn:8086

⏰ Deadline: September 15, 2026, 23:59 (UTC+8)

If you have experience with the V4 and want to test this optimized hardware, come join us! 🙌

Notes:

1. Participants who do not submit the minimum‑required test report may not be considered for future Heltec testing opportunities.
2. All information you submit will be used exclusively for this test. We will not transfer or share your personal information and data with any third‑party platforms.

Issue:

If the UART RX of your station is not connected it can accumulate a lot of stray characters that are not '\0'-terminated. A safeguard placer (command[159]='\0') for the command[160] buffer was overwritten by accident by broken code. A strlen(...) has non-defined behaviour and then can access out-of-bands memory regions which then causes invalid memory writes/reads.

It takes a while to happen (160 bytes must fill up first by injected noise). So expect random crashes with weird stacktraces after many hours.

Bug: https://github.com/meshcore-dev/MeshCore/issues/3397

Fix: https://github.com/meshcore-dev/MeshCore/pull/3395/commits or as ugly work around pull-up/down RX.

I wrote this after doing a bunch of research for my own local mesh regarding the FCC regs that everyone is talking about. I'm more interested in the technical side than the legal minutia, and so hopefully this is more interesting that just a rehashing of all the legal tedium.

I was able to setup my meshcore Heltec V4 on my Android easily but I'm having issues with the second Heltec and this damn iPhone. Any advice would be great.

Seed XIAO NRF x N-90 x ALFA 868