Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: export -import function not include some parameter #575

Open
bv3un opened this issue May 14, 2024 · 5 comments
Open

[Bug]: export -import function not include some parameter #575

bv3un opened this issue May 14, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@bv3un
Copy link

bv3un commented May 14, 2024

Category

Other

Hardware

Heltec V3

Firmware Version

2.3.9.f06c56a

Description

Export and import function not include some parameter like GPS position ,NTP server , licensed amateur radio.thus after firmware upgrade and import config need to setup again

Relevant log output

No response

@bv3un bv3un added the bug Something isn't working label May 14, 2024
@thebentern thebentern transferred this issue from meshtastic/firmware May 14, 2024
@bplein
Copy link

bplein commented Jan 9, 2025

I came here to open this bug, but see that it's been open for some time.

Use case #1: back up configuration with --export-config, and restore 100% of the settings via --configure.
Expected result: 100% of configuration is backed up and restored.
Actual Result: gps position, precision are not exported, so they cannot be imported.

Use case #2: scraping information via --info in order to check a setting.
Expected result: 100% of the configurable settings should be exposed via --info
Actual result: Not all settings are revealed. Example, GPS precision is revealed, but the GPS position, altitude are not.

@ianmcorvidae
Copy link
Contributor

NTP server is exported by --export-config, as is fixed position. I'm not sure where you're seeing it not export position, though it may not do so if you aren't using fixed position (since it wouldn't be useful to do so anyway). It does appear that the is_licensed field isn't exported along with the other ownership fields, though. Position precision only needs to be exported in a couple places. One is in the mqtt settings under mapReportSettings, where it is; the other is in channel settings, which is included within the channel URL. Within --info, position and altitude will be within the nodes data structure -- they're not configuration parameters in the same way other things are.

Other than the is_licensed field I don't think there's anything here to fix.

@bplein
Copy link

bplein commented Jan 9, 2025

Thank you for responding so quickly!

For --export-config, fixedPosition: <boolean> is exported, but not the actual position information. This means that setting a fixed position on a node is not backed up, and replacing or re-imaging that node, the full configuration cannot be restored.

Example from my export

  position:
    broadcastSmartMinimumDistance: 100
    broadcastSmartMinimumIntervalSecs: 60
    fixedPosition: true
    gpsUpdateInterval: 120
    positionBroadcastSecs: 10800
    positionBroadcastSmartEnabled: true
    positionFlags: 3

I found this by having to restore a setting to a node, where i have a fixed position that is not exactly where the node is located. I checked from another node, and it was reporting the position of my phone, not the expected values from my previous --setlat etc.

@ianmcorvidae
Copy link
Contributor

ianmcorvidae commented Jan 9, 2025

The position information is exported under the location header, outside of the config block, for reasons that have to do with the firmware implementation. The position settings section controls how position is managed, vs what actual location is used, basically.

In your export you should see first a channel_url, then config with a number of sub-sections, then location, module_config with subsections, and finally owner and owner_short

@bplein
Copy link

bplein commented Jan 9, 2025

Interesting. My T-beam is correctly showing location header by my RAK is not. I was only looking at my RAK4631 device when I commented on this issue.

I wonder if there's another setting that might be preventing location header from being populated.

Thank you for your patience with me. It's on my end it appears.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants