-
Notifications
You must be signed in to change notification settings - Fork 185
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]: Using yaml file to configure "modemPreset" and "region" causes the settings not to be applied. #573
Comments
debug output:
|
Doing it manually:
-> Works, But the device didn't reboot immediately. Only after executing it a second time. |
Same thing for modem_preset - via config file: not applied. Trying manually seems to work.
|
Same issue for hopLimit, txPower,.. Also one observation, is that whenever these settings are applied: the reboot afterwards is hit-and-miss. |
So it would seem it isn't rebooting reliably after the configure imports the yaml? |
Correct - tested on 2 devices, with full erase + firmware load. |
#576 seems related. |
I've since found a solution on my end for my requirements. Something worth noting is that if you are setting the |
I experience this problem too. channel_url is included in my yaml. Does someone have an explanation why this is open since May and not even confirmed? From my understanding exporting and restoring configs is quite a common task. |
using
meshtastic --host xxx.xxx.xxx.xxx --configure file.yaml
With the following lora config:
.. the "modemPreset" and "region" do not get applied on a freshly "wiped and flashed" device.
Hardware:
Heltec v3.1
Firmware:
2.3.7.30fbcab
Meshtastic Python API:
2.3.8
The text was updated successfully, but these errors were encountered: