I'm taking a look at the timeslot API example here, which was linked to in the answer to this question.
Very interesting! As I gather from the documentation for S110 and S130, it is still that case that a connected peripheral can advertise as a broadcaster while connected, but the API doesn't allow connectable advertising.
I'm trying to determine if doing so would violate the BLE spec somehow. I'm testing out this setup:
- Continue sending connectable advertisements while connected.
- Include a flag in manufacturer specific data that shows the peripheral status (busy/available).
- If available, disconnect from the current device when a different device attempts to connect.
- Ignore new connection attempts while busy.
I realize that dropping the connection and connecting to a new device would not happen on the first attempt, especially if using the TS API. But I think it would allow me to detect the connection attempt, drop the existing connection, and place my device in a state to connect to the new device.