Description
Before submitting
- I have searched existing issues to make sure this bug hasn't already been reported
- I have updated to the latest version of the software to verify the issue still exists
- I have cleared cache/cookies/storage or tried in a private/incognito window (if applicable)
Hardware
Heltec V3
Connection Type
HTTP
Local or Hosted
Firmware Version
v2.6.4.b89355f
Operating System
Ubuntu 24.04.2 LTS
Browser
Chrome Version 134.0.6998.165 (Official Build) (64-bit)
Expected Behavior
I want to start with a fresh device and configure it with a static IP of 192.168.1.201.
A freshly flashed Heltec V3 will be receptive to a serial connection from either my PC or Android phone.
From an Ubuntu PC, I run the following bash script.
meshtastic --port --set lora.region "US"
sleep 15s
meshtastic --port \
--set-owner-short "CE44"\
--set network.wifiSsid '█████████' \
--set network.wifiPsk ███████ \
--set network.addressMode DHCP \
--set network.wifiEnabled true \
--set network.ntpServer meshtastic.pool.ntp.org \
--reboot > ~/Documents/personal/ham/Pluto/B4F8.mt
sleep 15s
meshtastic --port \
--set network.ethEnabled true \
--set network.ipv4Config.ip 3540101334 \
--set network.ipv4Config.dns 16885952 \
--set network.ipv4Config.subnet 16777215 \
--set network.ipv4Config.gateway 16885952 \
--reboot > ~/Documents/personal/ham/Pluto/B4F8.mt
After that, I should be able to use the webui > Config > network window to alter addressMode and ipv4Config.ip. After I click the Save icon, I should get a "Delivery confirmed" notification.
In the alternative, I should able to run either of these two commands:
meshtastic --host 192.168.1.45 --set network.addressMode STATIC
meshtastic --port --set network.ipv4Config.ip 3540101334 --set network.addressMode STATIC
Actual Behavior
When I use the webui > Config > network window to alter addressMode and ipv4Config.ip and click the Save icon, I should get a "Delivery confirmed" notification. If I click to Message and return to Network, the old values DHCP and are still there.
When I run either of these two commands
meshtastic --host 192.168.1.45 --set network.addressMode STATIC
meshtastic --port --set network.ipv4Config.ip 3540101334 --set network.addressMode STATIC
I get notification of success. then Iwait for a half a minute for the device to reboot and join the network, nothing doing. A scan of the network does not show the device.
I can successfully use an Android device connected by USB-C to (first) change the mode to STATIC while leaving the IP address the same as assigned by the router, then (second) change the IP address to what I want.
Steps to Reproduce
(1) start with a freshly flashed Heltec V3. Firware v2.6.4.b89355f
(2) run this script:
meshtastic --port --set lora.region "US"
sleep 15s
meshtastic --port \
--set-owner-short "CE44"\
--set network.wifiSsid '█████████' \
--set network.wifiPsk ███████ \
--set network.addressMode DHCP \
--set network.wifiEnabled true \
--set network.ntpServer meshtastic.pool.ntp.org \
--reboot > ~/Documents/personal/ham/Pluto/B4F8.mt
sleep 15s
meshtastic --port \
--set network.ethEnabled true \
--set network.ipv4Config.ip 3540101334 \
--set network.ipv4Config.dns 16885952 \
--set network.ipv4Config.subnet 16777215 \
--set network.ipv4Config.gateway 16885952 \
--reboot > ~/Documents/personal/ham/Pluto/B4F8.mt
Try to use the webui to change mode from DHCP to STATIC.
Relevant console output
Screenshots
No response
Additional Context
"network": {
"wifiEnabled": true,
"wifiSsid": "████████████",
"wifiPsk": "████████████",
"ntpServer": "meshtastic.pool.ntp.org",
"ethEnabled": true,
"ipv4Config": {
"ip": 3540101334,
"gateway": 16885952,
"subnet": 16777215,
"dns": 16885952
},
"addressMode": "DHCP",
"rsyslogServer": "",
"enabledProtocols": 0
},