I searched for the hardware on that list, and thought the Asus USB-BT400 (*) was cheap enough to order and give it a try.įor the BT400 to function under Noble, I also needed to circumvent the normal driver installation process and instead install WinUSB so Noble can directly access the hardware to bypass Windows’ Bluetooth stack. Not surprisingly, the chip on board my experimental laptop was not on the list. Searching on that error message, I found more information in this GitHub issue filed against Noble, which pointed to a Noble document explaining that support is limited to a fixed list of hardware. Quite unlike the typical recoverable JavaScript exception I’ve become spoiled by. There are some native code components that were built for Noble support, and if things go sour in native code, it fails like native code, hence the jarring failure. Looking at the crash stack, the culprit appears to be Noble, the Node.js BLE module upon which the Node-RED extension was built. No compatible USB Bluetooth 4.0 device found! Getting node-red-contrib-noble-bluetooth set up and launching a flow was easy, but attempting to discover nearby BLE devices caused Node-RED itself to crash. So I wanted to see if BLE can be just as easy. I’ve had success so far with Node-RED making hard things easy, most recently in reading battery power state in an old Windows 10 laptop. I’ve known Bluetooth Low Energy (BLE) to be a new technology that can still be challenging to interface with.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |