I've been doing a lot of investigation into BluetoothLE and JS/Node Red.
Noble seems to be library of choice, maybe with Noble-Device on top.
However, it strikes me that some features of BluetoothLE communications are machine-global aspects. E.g. scanning can be turned off by another (node-red-node/process), so preventing your node from working.
Discovery aspects and connections are also probably system wide.
There are a number of Node-Red nodes which use Noble (the one I'm looking at is node-red-contrib-eq3-bluetooth), and I personally intend to expand my list of BLE devices in use for home automation (temp/humidity, heating control, beacons, tags, etc.).
I've been through hoops to allow for accessing multiple devices, dealing with connect/disconnect/missconnect/distant devices which appear on scan but don't connect, and the noble bug which stops scanning when a device is discovered.
Before I embark on reworking the mentioned node to suit my nefarious purposes, I was wondering if anyone had thoughts on BluetoothLE in general with respect to NR; whether we should agree some common concept of some global structure in NR, a kind of agreed way of using Noble (and if it is the library of choice) in node-red nodes so that the nodes can 'play nicely' together; or whether this is even required?
Answers on postcards attached to this thread :).