Peripheral connecting to multiple centrals experimental?

[Jakob]

Hi

We are trying to find a solution to connecting a BLE peripheral to a "preferred" or "primary" central. We are considering having the peripheral connect to multiple centrals and have the central tell the peripheral if it is a primary central. When a connection is made to a primary central other centrals are then disconnected, so only one connection is held.

This product will be in mass production, so we have two concerns:

1. Is this the best way of achieving this?

2. The ble_app_multiperipheral example is still experimental. Does this mean that this type of functionality is not recommended for production environments?

[FormerMember]

1. In BLE, the  best/and fastest way to make sure a peripheral connects to a preferred central is to use directed advertising. When using directed advertising, the address of the central to connect to is included in the advertising packet, and all other centrals should ignore that advertising packet. To do so, the peripheral the peripheral (obviously) has to get the central address before it can do the directed advertising.
    Another option is to allow the peripheral to connect to both centrals, and then the peripheral the disconnects from the one that is not correct one. (A peripheral cannot initiate a connection, only advertise to let the central devices know it is present, then the centrals can request a connection.)
2. Experimental means that one or more features in the example have not been fully tested from our side. We therefore cannot say that it has production quality, but you can test the example and check if it works in your usecase.