Preferences settings sometimes not sticking / saving. CLI 2.2.22 Firmware 2.2.24 App 2.2.24

I have 3 Heltec version 3 and I’m having random problems with settings not “sticking”, both via command line and app.

Meshtastic cli version 2.2.22
Android app version 2.2.24
Heltec v3 firmware version 2.2.24 (full clean install all on 3).

I found the (fairly old) issue below which seem to indicate that the problem has been resolved. But I’m still experiencing it.

“preference changes not saving in 1.1.8”

I thought it was only CLI, but I just updated my fixed position, and it didn’t stick via the app.

I have “cleaned” the command line input to ensure that there are no weird hidden unicode characters, or t0o many spaces, or silly things like 1 or 3 dashes before each “–set”.

I had more luck by always setting the region as the first thing after a flash, then waiting and setting other things.

That seems the most reliable, but then I noticed that, having set my “short name”, when I added a channel, it reset my short name to default.

This seems to be the same issue as experienced by a user on Discord:

“Sometimes after saving a setting - like enabling the telemetry module for example, I’ve noticed that the module says it’s enabled but when i disconnect and reconnect the device I see the setting wasn’t saved. It doesn’t happen all the time but it’s happened enough for me that I always double check my saved settings.”

So then I found this:

“1.3.40: CLI settings inputs break other settings? Just me?”

I’ve even tried grouping the settings by module, or setting each one individually and not chaining at all.
I’m using a good quality, new USB cable. I’ve even tried slowing the serial speed right down, but I don’t think it’s related to either of those because I always flash successfully at 921,600 and if it was data corruption, I’m sure a firmware update would feel it more than a few bytes of command line.

Of course, it’s proving impossible to reliably reproduce. Was thinking of writing a small script which would repeatedly make 1 or more settings, wait a few seconds, then read it back, compare the two, and log any that didn’t change (and run on a loop, say, 50 times doing a full re-flash every 10 times).

Would that be of any use, or is there a simpler way of doing it?

I’ve also posted this as a ticket at (can’t post github issue link here)

1 Like

Hi. I’m having exactly the same issue. I couldn’t add a fixed position, it always go back to 0. After your post I started to test and noticed that my long name has spaces. I reduced the long name and took out the spaces and it works, position was saved after first try.

1 Like

Fake news… work only for some time than resets to zero again. Firmware was beta 2.3.2 for Heltec V3. Will try the latest alpha firmware 2.3.3…

1 Like

I’m having the exact same issue, using a Heltec V3 and the latest stable firmware (“2.3.6.7a3570a Beta”, installed on June 1st, 2024).

No matter if I try to change the settings using serial or using the app, the changes I make won’t stick. After the Heltec reboots, it’s back to the firmware defaults. Any solutions?

Similar issue here only my client isn’t even loading the radio ID info anymore… worked previously (like last night). Using a RAK4631 and have tried flashing both 2.4.2.5b45303 Beta and 2.4.1.394e0e1 Beta multiple times. Please help. Client isn’t retaining config setting or saving them each time entered.

I have this problem (fixed position goes back to lat long height 0 m) on the RAK and T-echo. And Station G2… I think. Am getting used to it. I (also?) believe it is associated or correlated with changing the long name.