HCI Socket Broken since 1.5.x

[dwimberger]

1.5.x Versions don't work any longer together with @stoprocent/noble.

noble: Initialization of USB device failed: Cannot read properties of undefined (reading 'retryConnection')

At the moment, the only workaround is to use an override

"overrides": {
    "@stoprocent/bluetooth-hci-socket": "1.4.4"
 }

Sorry if this is brief, but I am still investigating the disconnect while connect issues we are seeing (similar to stoprocent/noble#16)

[stoprocent]

@dwimberger fix is on the way. This is why when you have a flu you should not code ;)
BWT ... are you using uart hci ?

[dwimberger]

I hope you get well soon :)
Yes, we are using uart hci currently with a NRF52 Dongle.

[stoprocent]

Nice 👍 I thought I was the only one doing it!
Did the latest update fix the issue?
Btw. I will have a look at the other issue you posted tomorrow or Friday

[dwimberger]

Yes, it seems to me that the new 1.5.2 fixes the issue.

Nordic has abandoned HCI for their BLE desktop application and are using BLE Serialization and a corresponding
pc-ble-driver-js

Is your HCI UART Sample build for the Nordic Vanilla Zephyr or built with the Nordic SDK and the SoftDevice Controller?

[stoprocent]

Have you seen this: https://github.com/stoprocent/node-bluetooth-hci-socket/tree/main/misc/nrf52840 ?
I am using the Vanilla HCI UART example from Zephyr but I did a couple of modifications to make it a bit nicer and more robust.
I did add little features like blinking LEDs on RX TX and increased the buffers

[dwimberger]

Yes :)

I did start from there but I used the latest Zephyr and adapted deprecated config settings. The buffers should be part of that config settings.

I cannot use a precompiled FW binary, so I guess if you have made other changes in source (Leds, stability?) these are not open or did I miss something?

[stoprocent]

I will post them in misc today. No secret there :)