You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: