When the hw goes into power save modes such as suspend (ie: systemctl suspend) the hardware may need to be reset for scanning to be allowed.
Specifically. Calling noble.stopScanningAsync never returns, deadlocking somewhere if called after returning from suspend state. Meanwhile, no no scan data will be returned. Also the noble.state does not indicate failure or scanning stopped.
Calling noble.startScanning... or noble.reset appears to place the hardware back into a known state.
When the hw goes into power save modes such as suspend (ie:
systemctl suspend) the hardware may need to be reset for scanning to be allowed.Specifically. Calling
noble.stopScanningAsyncnever returns, deadlocking somewhere if called after returning from suspend state. Meanwhile, no no scan data will be returned. Also thenoble.statedoes not indicate failure or scanning stopped.Calling
noble.startScanning...ornoble.resetappears to place the hardware back into a known state.