Cannot set lora.region

[Douile]

Versions

• python: 3.10
• meshtastic-python: abfcbe2
• meshtastic-device: 1.3.27, 1.3.30

What happened

Using serial connection setting the region (lora.region) to EU433 failed

$ meshtastic --set lora.region 2

$ meshtastic --set lora.region EU433

The CLI reports that the value is set and the device proceeds to restart but region remained unset

Expected outcome

The region changes to the correct value

Additional info

Not sure if this affects just this property or if it is an issue with other settings as well (further testing needed).

[Douile]

Upon further investigation, the debug output seems to show valid ADMIN packets being generated, but the serial log from the device shows no indication that these are being received.

I've tried regenerating protobufs to the same version used by the version of the firmware I was using but that didn't help.

What is also strange is --reboot (another admin packet) functions correctly.

[garthvh]

Are you using the pre release CLI version from pip? This is likely a firmware bug.

[Douile]

No I was using locally built version of master branch, commit mentioned above. I'm pretty sure the last version I tested from pip didn't work either but need to confirm.

The latest version of the android app configures fine so not sure if its the firmware or the CLI.

[Douile]

I was being an idiot, i wasn't leaving the device long enough to update the configuration before rebooting. It is strange though I had to leave the device (TTGO + heltecv2.0) a full minute after writing the configuration to get it to persist with serial. Over wifi it was a bit faster, 10 seconds did the trick, but instant reboot still dropped the changes.

[porkcharsui]

I'm not so sure this issue is resolved. Setting region via CLI appears to have no effect and does not display any error meshtastic --set lora.region US. Attempting to read back the setting change before or after a reboot still shows the value as unset. Via the iOS app 1.3.33 (72), I can successfully set region.

python: 3.9.13
meshtastic-python: 95e768e
meshtastic-device: 1.3.34

[garthvh]

You may need the latest python, there were protobuf changes in the last couple of firmware releases.

pip install --upgrade meshtastic --pre

meshtastic --set lora.region 1
meshtastic --get lora.region

meshtastic -- reboot
meshtastic --get lora.region

worked for me on a tlora v1

[porkcharsui]

I reflashed to reset the device to factory defaults and tried running meshtastic-python installed from latest commit on master.

meshtastic-python: 03aab10
firmware_version: firmware-tbeam-1.3.34.401b5d9.bin

This still appears to show lora.region value unchanged. I can however set other properties like owner and channel_url.

(meshtastic) bash-5.1$ meshtastic --get lora.region
Connected to radio
lora.region: 0
Completed getting preferences
(meshtastic) bash-5.1$ meshtastic --set lora.region 1
Connected to radio
Set lora.region to 1
Writing modified preferences to device
(meshtastic) bash-5.1$ meshtastic --get lora.region
Connected to radio
lora.region: 0
Completed getting preferences

Per your comment @garthvh I then tried the PyPy release but the same thing happened:

(meshtastic) bash-5.1$ pip install --upgrade meshtastic --pre
Collecting meshtastic
  Downloading meshtastic-1.3a21-py3-none-any.whl (75 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 75.9/75.9 kB 2.1 MB/s eta 0:00:00
Requirement already satisfied: pyserial>=3.4 in /Users/derek/.local/share/virtualenvs/meshtastic-hTyoJjiu/lib/python3.9/site-packages (from meshtastic) (3.5)
Requirement already satisfied: pexpect>=4.6.0 in /Users/derek/.local/share/virtualenvs/meshtastic-hTyoJjiu/lib/python3.9/site-packages (from meshtastic) (4.8.0)
Requirement already satisfied: pyqrcode>=1.2.1 in /Users/derek/.local/share/virtualenvs/meshtastic-hTyoJjiu/lib/python3.9/site-packages (from meshtastic) (1.2.1)
Requirement already satisfied: timeago>=1.0.15 in /Users/derek/.local/share/virtualenvs/meshtastic-hTyoJjiu/lib/python3.9/site-packages (from meshtastic) (1.0.15)
Requirement already satisfied: pyyaml in /Users/derek/.local/share/virtualenvs/meshtastic-hTyoJjiu/lib/python3.9/site-packages (from meshtastic) (6.0)
Requirement already satisfied: protobuf>=3.13.0 in /Users/derek/.local/share/virtualenvs/meshtastic-hTyoJjiu/lib/python3.9/site-packages (from meshtastic) (4.21.4)
Requirement already satisfied: tabulate>=0.8.9 in /Users/derek/.local/share/virtualenvs/meshtastic-hTyoJjiu/lib/python3.9/site-packages (from meshtastic) (0.8.10)
Requirement already satisfied: pypubsub>=4.0.3 in /Users/derek/.local/share/virtualenvs/meshtastic-hTyoJjiu/lib/python3.9/site-packages (from meshtastic) (4.0.3)
Requirement already satisfied: dotmap>=1.3.14 in /Users/derek/.local/share/virtualenvs/meshtastic-hTyoJjiu/lib/python3.9/site-packages (from meshtastic) (1.3.30)
Requirement already satisfied: ptyprocess>=0.5 in /Users/derek/.local/share/virtualenvs/meshtastic-hTyoJjiu/lib/python3.9/site-packages (from pexpect>=4.6.0->meshtastic) (0.7.0)
Installing collected packages: meshtastic
Successfully installed meshtastic-1.3a21
(meshtastic) bash-5.1$ meshtastic --get lora.region
Connected to radio
lora.region: 0
Completed getting preferences
(meshtastic) bash-5.1$ meshtastic --set lora.region 1
Connected to radio
Set lora.region to 1
Writing modified preferences to device
(meshtastic) bash-5.1$ meshtastic --get lora.region
Connected to radio
lora.region: 0
Completed getting preferences

[Douile]

I think it might be firmware issue with serial connections, using wifi it worked fine. Over serial had to set region wait a minute the restart the device and it took effect.

[porkcharsui]

I think it might be firmware issue with serial connections, using wifi it worked fine. Over serial had to set region wait a minute the restart the device and it took effect.

Are you saying you had success with serial? I tried waiting 90 seconds and then rebooting but didn't seem to see it stick ever. iOS application had no issue setting this value.

(meshtastic) bash-5.1$ meshtastic --set lora.region 1 && sleep 90
Connected to radio
Set lora.region to 1
Writing modified preferences to device
(meshtastic) bash-5.1$ meshtastic --get lora.region
Connected to radio
lora.region: 0
Completed getting preferences

(meshtastic) bash-5.1$ meshtastic --reboot
Connected to radio
INFO file:node.py reboot line:493 Telling node to reboot in 10 seconds
(meshtastic) bash-5.1$ meshtastic --get lora.region
Connected to radio
lora.region: 0
Completed getting preferences

[Douile]

Serial did work but questionably, I was using the master branch and I believe I also updated protobufs. The android app also works completely fine but the web app does have issues with serial as well which makes me wonder whether it is something to do with linux.

[porkcharsui]

@Douile Your last comment made go back and double check that I pulled the correct proto submodule and from latest commit 03aab10. I repeated the previous tests but have the same outcome.

All my test performed on macOS 12.4, and previously meshtastic 1.2 and same macOS version previously worked.

Is there a way to simultaneous output raw debug logs over serial, while setting this value so I can debug from the firmware side?

[mkinney]

Looks like you're using bash from Windows. Can you try again using just a command prompt? (not a power shell prompt either)

[porkcharsui]

Looks like you're using bash from Windows. Can you try again using just a command prompt? (not a power shell prompt either)

I'm am using macOS 12.4. You're likely seeing my use of pipenv to manage my virtualenv for python.