set lora.region and hop_limit unreliable

[roberthadow]

I use CLI to configure a stable of radios, Heltec V3 and V4. Each radio has its own bash script of particulars. Then I use a common script to write the specific configuration elements (example: IP address) and all the common elements (example: description of my LAN) to the device.

Here is a result. CLI claims that the configuration elements are set, then written, then committed. Immediately after, I --get those element that I can, to see if they are on the device.

Look specifically at the region and hop limit. They are set, written, and committed. When I check, no dice.

1 Set region US and owner -- USB
Thu Jun 25 09:11:41 AM EDT 2026
Connected to radio
INFO file:node.py reboot line:620 Telling node to reboot in 10 seconds
sleep
Connected to radio
Setting device owner to W2NJ Yagi 4524 and short name to 4524
Set lora.region to US
Set lora.hop_limit to 7
Set network.ipv4Config.ip to 3372329152
Set network.wifi_enabled to true
Set security.public_key to base64:[correct value redacted]
Adding 'base64:[correct value redacted] to the admin_key list
Writing modified preferences to device
Using a configuration transaction
INFO file:node.py beginSettingsTransaction line:634 Telling open a transaction to edit settings
Writing network configuration to device
Writing security configuration to device
Writing lora configuration to device
INFO file:node.py commitSettingsTransaction line:648 Telling node to commit open transaction for editing settings
Connected to radio
INFO file:node.py reboot line:620 Telling node to reboot in 10 seconds
 
Connected to radio
lora.region: 0
lora.hop_limit: 3
network.ipv4_config: ip: 3372329152
gateway: 16885952
subnet: 16777215
dns: 16885952

network.wifi_enabled: True
Completed getting preferences