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
I am running node-red on macOS (Monterey 12.1). I am new to node-red and simply want to read BLE sensor data from a peripheral (TI LPSTK-CC1352R) on my macbook.
I am using the node-red-contrib-generic-ble 4.0.3, it installs fine (Screenshot below), I follow the instructions for configuring the 'Generic BLE Out' node.
Here's the issue. On enabling 'BLE Scanning' nothing shows up ! My terminal window does say '[info] [GenericBLE] Start BLE scanning' (Screenshot below) but no peripheral device comes up in the 'Scan Result' drop-down menu. The BLE sensor node is working. I verified by finding it on the Bluetooth app (LightBlue) so sensor is transmitting.
Could someone kindly point how to solve this issue ? Thanks.
I have checked that both the Terminal and Web Browser have the permission to use Bluetooth in the security and privacy setting of the laptop.
The text was updated successfully, but these errors were encountered:
Hi,
I am running node-red on macOS (Monterey 12.1). I am new to node-red and simply want to read BLE sensor data from a peripheral (TI LPSTK-CC1352R) on my macbook.
I am using the node-red-contrib-generic-ble 4.0.3, it installs fine (Screenshot below), I follow the instructions for configuring the 'Generic BLE Out' node.
Here's the issue. On enabling 'BLE Scanning' nothing shows up ! My terminal window does say '[info] [GenericBLE] Start BLE scanning' (Screenshot below) but no peripheral device comes up in the 'Scan Result' drop-down menu. The BLE sensor node is working. I verified by finding it on the Bluetooth app (LightBlue) so sensor is transmitting.
Could someone kindly point how to solve this issue ? Thanks.
I have checked that both the Terminal and Web Browser have the permission to use Bluetooth in the security and privacy setting of the laptop.
The text was updated successfully, but these errors were encountered: