--configure does not work reliably

[ndoo]

I'm not sure why but I cannot get --configure with a YAML file to work reliably.

Generally, seeing worse behaviour on ESP32-based devices than nRF52 devices. Various issues such as:

• Node not rebooting after output of INFO file:node.py commitSettingsTransaction line:634 Telling node to commit open transaction for editing settings, Writing modified configuration to device
• Node rebooting but none of the configurations took effect

I'm not really sure how to describe it further, but I can repeatably replicate it with my Heltec v4.

You may try some of the YAML files at https://github.com/Meshtastic-Malaysia/meshtastic-config-my-sg/tree/main/MY_919 to replicate.

[juergenRe]

I am preparing a PR for configure, so I can try to have a look into this. Can you please run the configure command with --debug option and post the output here? Then I might get clearer info where it blocks. Thank you.

[dwilliams]

I'm seeing the "Node rebooting but none of the configurations took effect" issue with my ESP32 devices. Attached are the outputs from a number of things:

• meshtastic --info from before the attempt
  t3s3.beforeconfigureattempt.20251107.txt
• meshtastic --info from after the attempt
  t3s3.afterconfigureattempt.20251107.txt
• meshtastic --debug --configure output from the attempt itself
  t3s3.configureattemptdebug.20251107.log
• meshtastic --export-config from before the attempt

# start of Meshtastic configure yaml
canned_messages: Hi|Bye|Yes|No|Ok
channel_url: https://meshtastic.org/e/#CgcSAQE6AggNEgwIATgBQANIAVAeaAE
config:
  bluetooth:
    enabled: true
    fixedPin: 123456
  device:
    nodeInfoBroadcastSecs: 10800
  display:
    screenOnSecs: 600
  lora:
    hopLimit: 3
    region: US
    sx126xRxBoostedGain: true
    txEnabled: true
    txPower: 30
    usePreset: true
  mqtt:
    encryptionEnabled: false
  network:
    ntpServer: meshtastic.pool.ntp.org
  position:
    broadcastSmartMinimumDistance: 100
    broadcastSmartMinimumIntervalSecs: 30
    gpsMode: NOT_PRESENT
    gpsUpdateInterval: 120
    positionBroadcastSecs: 900
    positionBroadcastSmartEnabled: true
    positionFlags: 811
  power:
    lsSecs: 300
    minWakeSecs: 10
    sdsSecs: 4294967295
    waitBluetoothSecs: 60
  security:
    privateKey: base64:YI4/an2azhllmRzY9xersJS7oR9fM0q4MWrC3N8KrX0=
    publicKey: base64:Y6jHVMlyOIQtxxT7Yc3Q/FVxkWa/jRxqawy2lIzSMEk=
    serialEnabled: true
module_config:
  ambientLighting:
    blue: 220
    current: 10
    green: 248
    red: 217
  cannedMessage:
    enabled: true
  detectionSensor:
    detectionTriggerType: LOGIC_HIGH
    minimumBroadcastSecs: 45
  mqtt:
    address: mqtt.meshtastic.org
    encryptionEnabled: true
    password: large4cats
    root: msh/US
    username: meshdev
  telemetry:
    deviceUpdateInterval: 2147483647
owner: Meshtastic f8dc
owner_short: f8dc

• meshtastic --export-config from after the attempt

# start of Meshtastic configure yaml
canned_messages: Hi|Bye|Yes|No|Ok
channel_url: https://meshtastic.org/e/#CgcSAQE6AggNEhUIARAGGPoBIAsoBTgBQANIAVAeaAE
config:
  bluetooth:
    enabled: true
    fixedPin: 123456
  device:
    nodeInfoBroadcastSecs: 10800
  display:
    screenOnSecs: 600
  lora:
    bandwidth: 250
    codingRate: 5
    hopLimit: 3
    modemPreset: SHORT_FAST
    region: US
    spreadFactor: 11
    sx126xRxBoostedGain: true
    txEnabled: true
    txPower: 30
    usePreset: true
  mqtt:
    encryptionEnabled: false
  network:
    enabledProtocols: 1
    ntpServer: meshtastic.pool.ntp.org
  position:
    broadcastSmartMinimumDistance: 100
    broadcastSmartMinimumIntervalSecs: 30
    gpsMode: NOT_PRESENT
    gpsUpdateInterval: 120
    positionBroadcastSecs: 900
    positionBroadcastSmartEnabled: true
    positionFlags: 811
  power:
    lsSecs: 300
    minWakeSecs: 10
    sdsSecs: 4294967295
    waitBluetoothSecs: 60
  security:
    privateKey: base64:YI4/an2azhllmRzY9xersJS7oR9fM0q4MWrC3N8KrX0=
    publicKey: base64:Y6jHVMlyOIQtxxT7Yc3Q/FVxkWa/jRxqawy2lIzSMEk=
    serialEnabled: true
module_config:
  ambientLighting:
    blue: 220
    current: 10
    green: 248
    red: 217
  cannedMessage:
    enabled: true
  detectionSensor:
    detectionTriggerType: LOGIC_HIGH
    minimumBroadcastSecs: 45
  mqtt:
    address: mqtt.meshtastic.org
    encryptionEnabled: true
    password: large4cats
    root: msh/US
    username: meshdev
  telemetry:
    deviceUpdateInterval: 2147483647
owner: Meshtastic f8dc
owner_short: f8dc

• And the config that is attempting to be applied

# start of Meshtastic configure yaml
channel_url: https://meshtastic.org/e/#ChQSBN6tvu8aBnNwcmF3bCgBOgIIIBIMCAE4AUADSAFQHmgB
config:
  bluetooth:
    enabled: true
    fixedPin: 123456
  device:
    role: CLIENT_BASE
    rebroadcastMode: LOCAL_ONLY
    nodeInfoBroadcastSecs: 10800
    buzzerMode: DISABLED
    ledHeartbeatDisabled: false
  display:
    screenOnSecs: 600
    use12hClock: false
  lora:
    hopLimit: 3
    region: US
    sx126xRxBoostedGain: true
    txEnabled: true
    txPower: 30
    usePreset: true
    modemPreset: SHORT_FAST
  mqtt:
    encryptionEnabled: false
  network:
    enabledProtocols: 1
    ntpServer: meshtastic.pool.ntp.org
  position:
    broadcastSmartMinimumDistance: 100
    broadcastSmartMinimumIntervalSecs: 30
    gpsMode: NOT_PRESENT
    gpsUpdateInterval: 120
    positionBroadcastSecs: 900
    positionBroadcastSmartEnabled: true
    positionFlags: 811
  power:
    lsSecs: 300
    minWakeSecs: 10
    sdsSecs: 4294967295
    waitBluetoothSecs: 60
    isPowerSaving: false
  security:
    privateKey: base64:YI4/an2azhllmRzY9xersJS7oR9fM0q4MWrC3N8KrX0=
    publicKey: base64:Y6jHVMlyOIQtxxT7Yc3Q/FVxkWa/jRxqawy2lIzSMEk=
    serialEnabled: true
module_config:
  ambientLighting:
    blue: 220
    current: 10
    green: 248
    red: 217
  detectionSensor:
    detectionTriggerType: LOGIC_HIGH
    minimumBroadcastSecs: 45
  mqtt:
    address: mqtt.meshtastic.org
    encryptionEnabled: true
    password: large4cats
    root: msh
    username: meshdev
owner: Meshtastic f8dc
owner_short: f8dc

(GitHub wouldn't let me upload the yaml configs for some reason)

[dwilliams]

Just tried downgrading the t3s3 device from 2.7.13 firmware to 2.6.11 (stable) firmware. Now I'm seeing the not rebooting after the commit and not all the settings are being applied. Looks like the device and lora settings are being applied, but not the channel settings.