I've heard this brought up before, but it's not on our roadmap currently. I'm happy to open a feature request to see whether it's something we want to plan for the future, because I can't recall any specific reason why we would decide against this.
The Bluetooth hardware on our existing wearables is not capable of operating as a master and a slave simultaneously. Since we must operate as a slave to connect to the paired mobile device, we are unable to operate in master mode to connect to Bluetooth sensors. Capabilities may change with devices that are released in the future, but we cannot enable this type of API on existing devices.
But the watch does Already connect to bluetooth sensors like a heart rate sensor, right? Do these sensors have to run as master or how is this possible?
But the watch does Already connect to bluetooth sensors like a heart rate sensor, right? Do these sensors have to run as master or how is this possible?
