I have been experiencing an issue on a number of Debian pi 2 devices. Every so often something in the bluetooth stack crashes and brings down hci0 (not sure why at this point). After bringing back up hci0 and successfully testing its abilities (with various tools such as bluetoothctl, hcitool lescan, python-bluez, and noble's own dependency bluetooth-hci-socket), I can't get a new instance of a noble app to move noble from the 'unknown' state.
I did a little logging in noble/lib/hci-socket/hci.js Hci.prototype.onSocketError and found the error.message to be File descriptor in bad state.
Currently trying to trace where/what/why that error comes from and how to fix without a full reboot.
I have been experiencing an issue on a number of Debian pi 2 devices. Every so often something in the bluetooth stack crashes and brings down hci0 (not sure why at this point). After bringing back up hci0 and successfully testing its abilities (with various tools such as
bluetoothctl
,hcitool lescan
,python-bluez
, and noble's own dependencybluetooth-hci-socket
), I can't get a new instance of a noble app to move noble from the'unknown'
state.I did a little logging in noble/lib/hci-socket/hci.js
Hci.prototype.onSocketError
and found theerror.message
to beFile descriptor in bad state
.Currently trying to trace where/what/why that error comes from and how to fix without a full reboot.