using userBind cause error on setFilter about node-bluetooth-hci-socket HOT 9 CLOSED

@slashmili please see: https://github.com/sandeepmistry/node-bluetooth-hci-socket#user-channel

For user channel the adapter must be powered down before starting the Node.js app as per the documentation.

from node-bluetooth-hci-socket.

@sandeepmistry as I mentioned in the output I already powered down the device

sudo hciconfig hci0 down
sudo node le-scan-test.js
...

from node-bluetooth-hci-socket.

@slashmili apologies for missing this.

I believe setFilter is only applicable for bindRaw and not bindUser mode, as you are still getting an the events.

Could you please submit a PR to read me to document this?

from node-bluetooth-hci-socket.

Sure!

Does it mean that in noble/hci.js, there should be a checking to only call setSocketFilter if HCI_CHANNEL_RAW is set?

The reason I'm interested to these details is, I'm porting this library to Erlang and planning to use it in Nerves

from node-bluetooth-hci-socket.

Does it mean that in noble/hci.js, there should be a checking to only call setSocketFilter if HCI_CHANNEL_RAW is set?

Yes, I agree. It currently ignores the error event of "File descriptor in bad state" - but it would be clearer to not call setSocketFilter as you suggested. Do you have time to submit a PR for this as well?

from node-bluetooth-hci-socket.

Of course! I'll do this this week

from node-bluetooth-hci-socket.

@slashmili any progress on the PR?

from node-bluetooth-hci-socket.

@sandeepmistry no sorry I'm still pretty busy moving 🚚

from node-bluetooth-hci-socket.

Just for the record I found this explanation

Using this new facility does not require any external library or special
ioctl or socket filters. Just create the socket and bind it. After that
the file descriptor is ready to speak H:4 protocol.

http://www.spinics.net/lists/linux-bluetooth/msg37345.html

from node-bluetooth-hci-socket.