forked from noble/node-bluetooth-hci-socket
-
-
Notifications
You must be signed in to change notification settings - Fork 48
Open
Description
Hi guys,
We are developing an application that uses noble for central and bleno for peripheral. Here we were facing the socket error whenever we try to switch from central to peripheral or vice versa.
Error: EALREADY, Operation already in progress
To handle this we used to delete the socket and reinitialize it whenever we switch from central to peripheral or vice versa.
We just wanted to know is this a good approach?
(Note: Either noble or bleno will be active at a time).
is it possible to use the common HCI socket for both noble and bleno instead of creating the new socket every time whenever we switch from central to peripheral? or is there any alternative or best approaches for this?
Metadata
Metadata
Assignees
Labels
No labels