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
Here's the two peripherals (curie chip device and esp32) viewed using the android NRF Connect app from android:
As you can see, the curie device is advertising a service uuid, and the esp32 isn't. Is this a bug, or perhaps am I missing a step?
btw, thanks for creating ESP32_BLE_Arduino !
The text was updated successfully, but these errors were encountered:
Just modified the BLE_notify example to add a line to advertise the service:
In your video demo of this example sketch with web bluetooth you had to filter by name and specify
optionalServices
with the service uuid.When a BLE peripheral advertises a service, you can just filter by
services
without a name or the optionalServices property.I have a sketch for the Arduino 101/ TinyTile that has a working service advertisement: https://github.com/monteslu/ble-io/blob/master/arduino/curie_plus/curie_plus.ino#L127
(This sketch exposes a generic GPIO service I've been connecting to for johnny-five/nodebots)
Here's the two peripherals (curie chip device and esp32) viewed using the android NRF Connect app from android:

As you can see, the curie device is advertising a service uuid, and the esp32 isn't. Is this a bug, or perhaps am I missing a step?
btw, thanks for creating ESP32_BLE_Arduino !
The text was updated successfully, but these errors were encountered: