Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
We will be using a master 20737s to connect multiple 20737s slaves. We would like to connect with pairing and by looking at the hello client and hello sensor examples the API only accepts one key. The questions is how to manage multiple connections where each of them has its own pairing key ?
As we can see the API is not "connection" aware, but it looks like it will use the same key for all the connections. More, our master will connect multiple devices and some of them will require pairing and some of them will not.
We have a pairing schema where the slave advertises itself and withing the manufacturer data advertises some data which is the used as a hashing algorithm to compute the pin code. The pin code thus changes once in while and is not fixed. That's why we need to be able to set pairing keys for each device.
Moving forward we will probably have to wait for a SDK release. Do you have any timing about that ?