Heltec MeshTower resets its configuration itself

@richard3366 erase-flash, update etc + setting discharge to -20 didn’t resolve the issue, as it just froze again.

if the battery power is too low or other factors trigger the protection circuit, the battery supply may be cut off.

There were no obvious triggers for a cut-off, charge still ~90% but

If there is faint light (e.g., at dawn), the solar panel may attempt to power the MCU directly, but the voltage is low and unstable. This can cause the nRF52840 to repeatedly power on and off, eventually leading to configuration loss or device freezing.

The latest freeze (just now) did happen when the sun came around late in the afternoon.

Are you advising to bypass the R23 resistor? Or what is the plan here?

I’m curious to know, when @richard3366 said “Latest Findings on Device Freezing Issues”, was this somehow interpreted as being a temperature related issue?

If so, the phrase relates to the processor getting stuck - frozen as in not moving, not frozen as in the temperature.

Most commercial electronic components are spec’d to 0 to 70℃ and industrial can do -40 to 85℃. If a circuit is in a box, it tends to be warmer than air temperature as the activity generates heat, so for casual use, commercial components in a relatively well sealed case can do sub-zero temperatures. MCU’s tend to work down to very low temperatures - small thermal mass, they keep themselves warm and no liquids.

Batteries however are a whole different thing and no settings can get around the fact that they are chemistry based with enough liquid / sludge / goo that their power delivery capacity falls off a cliff when they get cold. And whilst you can get power out of a LiPo at -20℃, they shouldn’t be charged until they get back to 0℃ - which in real terms means doing nothing more than sending a message out that says the unit is too cold to do any serious work.

So the min/max temperature settings are about turning off charging for the specific chemistry of the batteries in use so they aren’t damaged (charged whilst too cold) or exploded (charged whilst too hot). The settings can’t make things work because the environment is out of limits.

Insulation &/or some heater element can help, as long as the solar panel can run a heater as well as charge. If the battery case is closed from the elements and insulated, it doesn’t take much to warm up the batteries via solar with a 10W resistor - sometimes even taking power from the batteries themselves if you can juggle the numbers on using battery power to enable the solar to then make up what was used and some more beyond.

Your next challenge at this point is keeping the solar panel clear of ice & snow …

The issue is that the device is going to an unresponsive state (frozen) while temperature and battery charge are within parameters. This remains, no recovery until RST button is physically pressed; there is no other way to regain normal operation.

As suggested, low light on panel during protected state (while out of boundary temperature/low battery) might be causing the issue. I am stating that the unresponsiveness also happens while within the BMS parameters, so during normal operations with no sleep/protective mode.

I understand that.

What I was querying was the bit about changing the discharge temperature threshold which will only help if the unit’s batteries are dropping below freezing. I don’t see @richard3366 suggesting this as a change.

What would be useful as a test would be to locate it somewhere where permanent power can be applied to see if it can run for many hours/days without issue.

As the default for discharge temp is 0, lowering this value would reduce the occurrence of the low-temp battery protection node, where @richard3366 noted that the issue might occur (low light during protected mode).

I observed the issue also occurring while in normal mode. As such, the statement that the issue occurs only in protected mode isn’t applicable.

2 Likes

Have you been able to find a way to change bms setting?

Instructions on how to get the device working with meshtastic firmware are at https://flash.nmiot.net:3333/ at the end of https://wiki.heltec.org/docs/devices/open-source-hardware/nrf52840-series/mesh-solar/usage-guide

Only when I checked the “redifine com” box did it work for me.

@richard3366 any insights / plans how to resolve the issue at hand?

If there is faint light (e.g., at dawn), the solar panel may attempt to power the MCU directly, but the voltage is low and unstable. This can cause the nRF52840 to repeatedly power on and off, eventually leading to configuration loss or device freezing.

Hi, so i have kind of the same problem here.
I recived my meshtower about a month ago. I charged it up once, flashed the 2.7.15 firmware onto it.
It doesn’t freeze, but it reboots about every 10 minutes out of nowhere. the meshtower sits in my basement at a stable temperature of about 24°C wich shouldnt be a problem. sometimes it also resets its config, but i am able to connect to it via bluetooth.

So, i received a new updated module and after installing this am also observing reboots every +/- 9 minutes.

I also observed a lockup due to sundown/light conditions but this was before additional installation steps, so might be resolved with the watchdog (which now causes a reboot every 9 minutes).

that may be, i have it running without anything plugged in (no USB and no Solar).
The rebooting on its own isnt the big of a deal but the resetting still is.
it would be nice to know if its a bms problem or a nrf problem

i will try a alpha firmware and see if the behavior changes

i upgraded to 2.7.17 today, issue still presists

My new mestower is doing the same. It intermittantly becomes unreachable. Shows battery as " 0 / 0.95v" when fully charged. Meshcore Firmware version v1.11.0-6d32193 (build: 30 Nov 2025). I had it running Meshtastic for a week and it seemed more stable. It is still in the house as I dont trust it on my tower.

I just received a new LoRa module. I expected to receive a base/power distribution board as Richard indicated that they found an issue in that circuitry. How a new LoRa module is supposed to fix this is beyond me. I’ve asked for clarification, awaiting a response.

Hi, I am also experiencing problems and resetting the MESHTOWER device.

Tested two times with different temperatures (Street temperature -12 -16°C and House Attic house temperature +17°C) and with all the firmware’s presented

here

https://resource.heltec.cn/download/MeshSolar/firmware

  • firmware-heltec-mesh-solar-2.7.14.e959000.uf2
  • firmware-heltec-mesh-solar-2.7.15.567b8ea.uf2
  • meshsolar_meshtastic_2.7.4.uf2

and on Github Meshtastic Firmware 2.7.17.9058cce Alpha

The operating time before crashing / freezing and resetting all settings is 10-15 hours in any use, I also tried with and without the connected solar panel from the kit.

I noticed a feature that after the MeshSolar - BMS freezes, it does not respond to commands on Param Sync https://resource.heltec.cn/utils/flash to connect, you need to flash* Meshsolar BMS Stock Firmware (meshsolar_bms_0.0.1.uf2), then configure from scratch as a new device :cry:

Settings BMS Temp protection

I do have the same issue. Rebooting every 10 minutes or so. But even after disconnecting the solar panel, and disconnecting the battery. Then connecting it to a 20v USBC power source (two red leds). The same behavior persists. Reboot with some settings (like the clock) resetting. (Using Meshcore Firmware 1.11.0)

This has happened to me and was due to low battery brownout – if the battery dropped very low before shutdown, it might have caused corruption during the power-down sequence.

Check your batteries and set the shutdown voltage setting – In Meshtastic, you can set device.shutdown_on_battery_level or the minimum voltage threshold. Setting this a bit higher (e.g., 3.3V or 20%) gives the device time to shut down gracefully before the battery gets critically low.

I can confirm that i have the same problem. As soon as i flashed Meshcore 1.11.0, my meshtower worked for several days. After a shotdown, Now it just reboots every 9 -10 minutes… it doesn matter if is battery powered or connected to 20v USBC.

I have just

  • erased the flash using meshcore web flasher
  • rebooted into DFU and flashed meshsolar_bm_0.0.1.uf2 from : https://resource.heltec.cn/download/MeshSolar/firmware/bms
  • can confirm that MeshSolar WebSerial Tool https://flash.nmiot.net:3333/ works
  • flashed meshcore 1.11.0 using meshcore web flasher
  • once meshcore is flashed, the MeshSolar WebSerial Tool will not work anymore. I’m not sure if any changes on the BMS params are persisted or not…

I can confirm the meshtower keeps rebooting every 10 minutes…

Currently this is a huge disappointment, considering the cost of the meshtower!

Trying this now:

Patch for the 9-minute reboot with the new watchdog-module in Heltec MeshTower, MeshSolar & Heltec V4 -> https://github.com/meshcore-dev/MeshCore/pull/1446/commits/c89a0e9929f4247d40569f568ccb1d216cc66762

Patch is not merged in the project yet, therefore compiled firmware by Koen de Jong: https://share.procolix.eu/s/EnFtFHGaBYfaYxJ

1 Like

Flashed and i can confirm currently the uptime is over 42 minutes. I will put this on test and report it here.
Thank you @Kasper-86 for this links

Edit: 9h uptime. Looks like this patch works well!