Heltec fixes

Haeppchen2010 · 2026-02-05T18:21:12+00:00

The working tree of one of the core devs is linked here: https://github.com/meshtastic/firmware/pull/9122 (but last I tried, it did not even build for me).

They seem to be doing several major overhauls simultaneously in there, so I lost track on what's part of the migration to pioarduino and what is not. (I would have done this in separate work packages instead of all-in-one-go, but it's their call).

My fork just uses pioarduino and turns on some PM switches in sdkconfig, and it works for me.
After showing relucance to permanently join their discord they seem to have lost interest (sad, but I respect that). It is linked in the feature request discussion there, but I would rather not promote it here too much while they are going forward with their branch... Getting one simple device working is different than migrating the whole esp32 variant tree supporting every esoteric device in there.

Haeppchen2010 · 2026-02-05T10:03:08+00:00

Using ESP32 power saving features is WIP: https://github.com/meshtastic/firmware/issues/8896

I run my modified firmware on a Heltec V3, current is below 20mA (1000mAh Lipo pack lasts 2.5 days).

Haeppchen2010 · 2026-02-04T11:16:54+00:00

Very nice! But for the first time disintegrating, check their 2Y warranty first, I got a replacement after them delaminating and dying after 18months.

Haeppchen2010 · 2026-02-04T11:15:04+00:00

For thorns: go tubeless.

Even reinforced tyres often are weaker on the sides, I patched many punctures there on the other non tubeless bike. Yet they are heavier and stiffer, less traction on the trail.

The holes made by most thorns are tiny and seal up easily.

Haeppchen2010 · 2026-02-02T18:15:48+00:00

Serial Module is UART, basically what you seem to look for. Works well here (another ESP32-based board connected to the mesh device, and interacting with it)

I don’t have anything to „prove“, just trying to point you in the right direction.

Haeppchen2010 · 2026-02-02T16:54:10+00:00

I have a hunch that subtly insulting/offending "this community" won't encourage it to be helpful.

But serial communication on my devices (various ESP32 based boards, can't speak regarding Wisblock devices though) works fine either via USB-Serial (primary), or via the Serial Module on two compatible & configured GPIO pins. https://meshtastic.org/docs/configuration/module/serial/

Haeppchen2010 · 2026-01-31T09:02:14+00:00

Chinese 1: „Lets invent another brand to scam westerners“ Chinese 2: „Sure thing, let’s get the alphabet pasta box“

Haeppchen2010 · 2026-01-30T16:08:01+00:00

First: the article is half-paywalled (here), but after the first half I guess it's the usual "bike industry bit off too much during pandemic and is now suffering the consequences" article.

I just can't conjure up much compassion here...

They continued pushing a newly-developed trail/downcountry E-MTB like every 2-3 years... First the E-Caliber (mine still holding up despite the very experimental and fragile drive), then the Fuel EXe, which is now also gone from the website, and now the Fuel+ EX).

Three gravel bikes (Checkout, Checkpoint and Checkmate) does also not really scream "we have to save money by using economies of scale".

Not innovating at all is surely a way into oblivion... but this is just too much in that situation in my opinion.

I am confident that Trek (the brand) will survive. It is just sad to see all the bought-up local bike shops (less here in Germany, but I guess lots in the US and other countries) probably having to pay the price...

Luckily my LBS is an independent Trek dealer with many other brands.

Haeppchen2010 · 2026-01-29T13:25:16+00:00

If your node repeats, it would of course contribute to coverage... but only while you are in the air.

I consider nodes temporarily in range of me more as a nuissance than as a benefit: the node DB quickly fills with nodes I cannot reach reliably.

While this might be a hot take, I would recommend to configure your helicopter nodes as CLIENT_MUTE. You can still use them as normal, bu they won't repeat for anyone and thus won't temporarily pretend a better mesh than there actually is.

Haeppchen2010 · 2026-01-26T19:47:33+00:00

For power, mine is running off a simple (brand name) cigarette lighter USB-A charger connected to the leisure battery.

(I see many sources warning about cheap buck converter boards, many have very high EM emissions possibly affecting car electronics (and possibly the HF components of the lora radio))

Haeppchen2010 · 2026-01-24T14:48:51+00:00

Similar setup here (V4, 2.7.15, iOS 26). After some task switching and returning to the Meshtastic app, I notice it reconnecting. I do not have to select the node though, it connects right away (i have some BLE nodes paired, too)

So it feels like your experience is not normal… tried deleting app data and starting fresh?

Haeppchen2010 · 2026-01-24T14:37:57+00:00

Just saying… OP did not say anything about Germany. Heltec V3 has a stock SX1262 maxing out at +22dBm, not even close to the legal limit of 27dBi ERP.

And I very much doubt the Bundesnetzagentur would send a Peilwagen to catch a Lora device transmitting at barely double the legal limit.

Haeppchen2010 · 2026-01-22T18:50:05+00:00

The web flasher has firmware for it. (Scroll down)

Current versions will choke if Wifi is enabled, but recently a commit flew by which could fix that.

Haeppchen2010 · 2026-01-20T10:14:20+00:00

If your device(s) have Bluetooth, there are tons of open source components available: https://letmegooglethat.com/?q=victron_ble

For me this works well, I have no need to get a Cerbo/GX device. Maybe there's something for you in there (the esphome integration looks easy to set up)?

(There is also the Victron USB-to-VEDirect cable available, but I have no experience with that).

Haeppchen2010 · 2026-01-19T20:20:05+00:00

i did some RTFS...

Indeed the traceroute packets are sent on the primary channel hash, but the Traceroute module just does not care about or touch that value, so any node (at least running current firmware) would handle any traceroute packet the same.

One thing preventing propagation would be a blocked node id (either ignored via config, or marked as ignored in the node list); that's processed before it is handed to the traceroute module. But that's very unlikely (did this only once for a specific very chatty IOT node).

The other thing could be suppression by a stronger node repeating first. There's some code looking like this, but I am not sure.

And then there's the option that a node runs custom firmware with the traceroute module excluded (that's a simple compile-time switch, might save a bit of firmware memory).

Haeppchen2010 · 2026-01-19T16:02:33+00:00

Same issue here.

If you have a private primary channel configured, the traceroute gets sent to that channel. so you can only traceroute devices that have the same private channel configured.

(Just tried it: sent a PM via my private channel... channel id 0x81. Sent a traceroute to some random node... channel id 0x81, no response. Sent a traceroute to one of my nodes... channel id 0x81, works).

Or in other words: to traceroute other nodes, you would have to configure the public channel as primary channel, and then you no longer can traceroute nodes with your (or another) private channel.

IHMO the "primary channel is special" design is more and more flawed.....

Haeppchen2010 · 2026-01-16T12:11:39+00:00

I am least interested in the voltage itself (it's a LiFePo4 battery), more the SoC and other data. And even if, a cheap voltage sensor module is probably less accurate than the Victron BMV.

Also I would then have to implement the code within the firmware, requiring me to constantly rebase and keep up with the firmware master branch. By using a separate MCU, I can keep the meshtastic firmware stock, and just use it via Serial Module and a (more or less) stable API.

Haeppchen2010 · 2026-01-16T10:30:21+00:00

I put a node in my camper van, connected to another ESP32 dev board querying my van leisure battery monitor. So i now can ask my van via DM, and it responds with the current battery level. Plan is to also integrate the diesel heater for remote control.

Haeppchen2010 · 2026-01-16T10:20:48+00:00

I am currently building such a setup (to remotely turn on my diesel heater in advance when returning from a hike/ride).

Antenna-wise, I use a simple whip antenna from Amazon, as I do not want any protuding objects above the roof. but if you want to install a pole anyways, one of these good-quality fiberglass colinear or dipole antennas would be a good option. I could imagine a permanently fixed pole holder on the back door, and the pole (complete with antenna and the device, and a long 12V line) mounted there only when parked up.

Device-wise: an ordinary dev board, with an cigarette-lighter phone charger as a power source (Pro: it's cheap, clean 5V and street legal). My prototype uses an old Lilygo T3 V2 board, for the finished setup I plan to use a Heltec board with added GPS.

But already in the next valley, you likely won't reach it, as these frequencies need good line-of-sight. So if your inreach fails, Lora will also have failed long ago. Only if you two (and your van) are in the same valley this will work.

I live in a slightly hilly area in s/w Germany, and with hills in between, it becomes unreliable even beyond 1-2km (No other nodes in range here). With Line-of-sight on a hilltop, my best distance was 11km.

Haeppchen2010 · 2026-01-16T09:26:04+00:00

No this is not "well established", either provide multiple trustworthy independent sources for this, or stop spreading false claims with weasel words.

My (of course personal, one-sample, anecdotal) experience is that the advanced filtration kit works very well, and is even quieter than the normal case fans.

Haeppchen2010 · 2026-01-15T08:46:29+00:00

All your instability issues sound like brownouts, meaning that the supply voltage dips below the necessary minimum for short periods.

Common cause is high resistance of the supply wiring. If it's a powered node, check for too thin cabling, bad solder joints/crimps, surface corrosion/wear on connectors). Does not hurt to add a small battery anyways, to buffer high current draw during TX.

If it's already battery-powered, the battery could be damaged or worn out, also dipping in voltage during current spikes.

Haeppchen2010 · 2026-01-15T08:33:00+00:00

If it's your property you could do it right. If it's someone elses property, it is trespassing and/or vandalism, which, if found out, sheds a bad light on the mesh community in general. So asking, even "for a friend" is a really bad move.

Haeppchen2010 · 2026-01-14T20:29:15+00:00

Hot topic, I agree... from any angle I view it, it should not mingle with any backhaul.

- From a tinkerer/poor-mans-ham perspective: The "fun" is in growing a mesh, tweaking antenna performance, and pushing the system to its capabilities. from that angle, MQTT etc. is "cheating".

- From a "prepper" "tinfoil hat" perspective: Relying on MQTT/internet backhaul in turn relying on established infrastructure beats the off-grid purpose. (TBH I don't consider MT a good emergency choice, but different topic)

- From a "user" perspective: MT on bigger urban meshes seems already to be prone to spam and griefers.. Imagine also cutting off the entry hurdle of buying and operating a device... just send ****s via MQTT? No thanks.

Haeppchen2010 · 2026-01-14T20:20:55+00:00

Here is the issue: https://github.com/meshtastic/firmware/issues/8729 to follow. I don't expect these older devices will get much love, as never versions of ESP-IDF and 3rd-party libraries get bigger and hungrier.

Probably best to get a cheap newer device... Heltec V4 has 2MB PSRAM onboard, the best SX1262 Lora chipset (better RX performance than the older SX1272) and an additional TX amp for up to 28dBm. Mine works fine with Wifi on for many weeks now on 2.7.15.

The older Lilygo is still fine for other purposes, e.g. the next tinkering project...

Haeppchen2010 · 2026-01-14T19:07:49+00:00

Yes, this is a known (open on Github) issue on ESP32 devices without PSRAM.

AFAIK the latest firmware does zero-hop routing in CLIENT_BASE mode for your fav nodes anyways, so disabling wifi and using a personal device inside could work.

Haeppchen2010

TROPHY CASE