I installed Zadig 2.3. My CSR 4.0 dongle is visible as "Generic Bluetooth Radio", I installed the WinUSB Driver for it.
After this, the Bluetooth section disappeared from the device manager, and the Bluetooth on/off toggle switch in the devices overview was also gone. (This was not a problem for me, as I do not use any other Bluetooth peripheral with my PC.)
However, I like to ask whether this is expected behavior with the WinUSB driver installed?
But it made no difference. The native Web IDE did not recognize the dongle before (only a COM1 port, which seems to be another device) and it still does not recognize it now.
I then played around a few hours with removing and plugging the BLE dongle while installing, reinstalling and deinstalling drivers and devices in the device manager.
But for the native Web IDE nothing changed.
This is start of console log when having the native Windows-10 drivers:
We have chrome.serial - not using 'serialport' module
'noble' module couldn't be loaded, no node.js Bluetooth Low Energy Error: LIBUSB_ERROR_NOT_SUPPORTED
Disable Web Bluetooth as we have Winnus instead
serial_audio: Audio Sample rate : 48000
...
And this is with WinUSB drivers:
We have chrome.serial - not using 'serialport' module
Disable Web Bluetooth as we have Winnus instead
serial_audio: Audio Sample rate : 48000
...
Now I perhaps have missed something ... I must probably try something else.
Any help will be appreciated!
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Unfortunately I had no luck.
I installed Zadig 2.3. My CSR 4.0 dongle is visible as "Generic Bluetooth Radio", I installed the WinUSB Driver for it.
After this, the Bluetooth section disappeared from the device manager, and the Bluetooth on/off toggle switch in the devices overview was also gone. (This was not a problem for me, as I do not use any other Bluetooth peripheral with my PC.)
However, I like to ask whether this is expected behavior with the WinUSB driver installed?
But it made no difference. The native Web IDE did not recognize the dongle before (only a COM1 port, which seems to be another device) and it still does not recognize it now.
I then played around a few hours with removing and plugging the BLE dongle while installing, reinstalling and deinstalling drivers and devices in the device manager.
But for the native Web IDE nothing changed.
This is start of console log when having the native Windows-10 drivers:
And this is with WinUSB drivers:
Now I perhaps have missed something ... I must probably try something else.
Any help will be appreciated!
Best regards,
squyrrel