[Bug]: position_precision always shows "Within 23km" in web client and save does not trigger device reboot #1033
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
Rak4631
Connection Type
Serial
Local or Hosted
Firmware Version
2.7.15.567b8ea
Operating System
Mac OS 15.7.4
Browser
chrome 145.0.7632.162 (Official Build) (arm64)
Expected Behavior
Connected node to Mac via USB and opened the web client. Navigated to Radio Config → Channel Settings for the PRIMARY channel (PrivateCoon, Channel 0). The Location field displayed "Within 23 kilometers" despite the channel being configured with precise location. Attempted to change the precision setting and save via the web UI.
- The web client should accurately reflect the position_precision value stored on the device — in this case, precise location (position_precision = 32).
- Saving channel settings should trigger an automatic device reboot as expected when config changes are applied.
Actual Behavior
The web client displayed "Within 23 kilometers" regardless of the actual setting on the device. Attempts to change and save the precision value via the web UI had no effect — the value reverted to "Within 23 kilometers" after every reboot.
Critically, saving new settings from the web client did not trigger an automatic device reboot. The device had to be manually rebooted each time. After manual reboot, the precision value still reverted, confirming the save was either not being written correctly or not being written at all.
When checking the same channel via the Meshtastic mobile app over Bluetooth, the channel correctly showed precise location enabled. The map also confirmed precise location was working correctly, suggesting the actual stored value on the device was correct and the web client was both misreading and failing to write the position_precision field.
Attempting to set the value via Python CLI (python3 -m meshtastic --port /dev/tty.usbmodem112401 --ch-set module_settings.position_precision 32 --ch-index 0) timed out with no response, likely because the web client was holding the serial port open.
Steps to Reproduce
Connect a Meshtastic node to a Mac via USB
Open client.meshtastic.org in Chrome and connect to the device via serial
Navigate to Radio Config → Channel Settings for the PRIMARY channel
Observe the Location field — it displays "Within 23 kilometers" regardless of the actual precision setting stored on the device
Change the Location field to Precise Location and click Save
Observe that the device does not automatically reboot as expected after a config change
Manually reboot the device
Reconnect via web client and navigate back to Channel Settings
Observe that the Location field has reverted to "Within 23 kilometers" — confirming the save did not write to the device
Disconnect the web client browser tab and attempt to set precision via Python CLI (python3 -m meshtastic --port /dev/tty.usbmodem112401 --ch-set module_settings.position_precision 32 --ch-index 0)
Observe that the CLI command times out with no response, suggesting the web client held the serial port open even after attempting to disconnect
Connect to the same device via the mobile app over Bluetooth and navigate to the same channel settings
Observe that the mobile app correctly displays Precise Location enabled — confirming the actual stored value on the device was correct all along and the web client was misreading it
Relevant console output
Screenshots
No response
Additional Context
This appears related to issue #496 where the web client throws cannot use field meshtastic.ModuleSettings.position_precision with message undefined when saving channel settings. The web UI is displaying and saving position_precision incorrectly, failing to reboot the device on save, and blocking the serial port — while the mobile app handles the same setting correctly over BLE.