So starting with the 1.1 series of releases the firmware is smarter about power management. And part of that is that it assumes that if it has power coming in via the USB port it doesn’t need to sleep. This is really useful for most users because if they hook up external power the bluetooth stays always connected (or they can connect to the deivce over USB). But if you are trying to run a remote node for a long period of time on battery you do not want this.
If you are running a remote node that is battery/solar powered you’ll want one of the following to options:
“meshtastic --set-router” tells node to be power conscious and to only power up the screen/BLE if the user presses a button. Eventually will also imply that “this node has good line of sight and should be heavily weighted when routing”. This is the option you should probably use.
“meshtastic --set is_low_power true”. This option means “work like a regular node, with the normal sleep/wake pattern but even though you see power coming in on USB don’t constantly stay awake”. You probably don’t want this option but it is useful for some edge cases (‘solar powered node that still talks bluetooth to the app etc…’).
btw: Soonish (I just added this to my task queue) I’ll supplement the nice user manual ya’ll have been making with details on these optional / more geeky parameters.