`--export-config` and `--configure` as backup&restore not reliable

[Fuzzillogic]

I was expecting that --export-config i.c.w. a subsequent --configure was a suitable method to backup and restore node settings. While partially successful, there are some issues:

• On my T-Deck running 2.7.18 alpha I did $ pipx run "meshtastic[cli]" --export-config > config.yaml. The resulting config seems mostly complete. However, favorited nodes are missing from the export.
• After resetting my T-Deck, I tried to restore the configuration via $ pipx run "meshtastic[cli]" --config config.yaml.
  • The private and public key were not restored (properly). I had to restore them using MUI from on-device backup.
  • The channels were not configured.

The settings not imported (channels, keys) are part of the config.yaml. The output of --configure also indicates that they are set in the process.

I'm not using remote admin, so I don't know if those keys are properly backed-up and restored. Same goes for many other module settings.

I'm not sure if I'm just using it wrong, or due to incompatibility in protobufs (I'm using firmware 2.7.18), or if these are bugs. My main goal is to backup&restore settings, and this looked like the most promising method.

The T-Deck Plus is connected via USB serial, on Kubuntu 25.10. Using CLI version 2.7.6.