Typical BLE settings for a multi-device mouse

[DX_HK]

I am developing a BLE mouse that can connect to 3 devices using nRF52840.

The sample code (peripheral_hids_mouse) allows simultaneous connection to multiple centrals.

However, when looking at the operation of a typical multi-device mouse (for example, the Logi M650), it appears that only one device is connected at a time and only switches between them quickly.

There is no problem with the minimum operation of 1:1 pairing and communication.

Problems occur when pairing with a new device.

When I switch devices, after disconnecting from the old central (PC1), when I start advertising to connect to the new central (PC2), the old central (PC1) connects.

When switching devices, the connection with the old central (PC1) is disconnected.
Advertising begins to connect to the new central (PC2).
At this time, the old central (PC1) will connect.

By changing the ID, it is possible to make it appear as if it is advertising a different device.
However, in that case, it will appear to the central (PC1) as just another mouse.

When I noticed this problem, I realized that I probably didn't have knowledge of the internal implementation of a standard BLE mouse.

I would be happy if you could either directly tell me how to solve this problem or provide me with the source code for a multi-device BLE mouse that I can use as a reference.
Could you please help me?

[Edvin]

Hello,

How exactly did you implement it at this point? What do you change when you change to device 2 in your application?

By changing the ID, it is possible to make it appear as if it is advertising a different device.
However, in that case, it will appear to the central (PC1) as just another mouse.

I believe this is how it is typically done in the typical mice that can connect to several devices. They are using one ID for each. 

At least I believe that is how they do it in the logi devices that can handle multiple connections. It will appear to PC1 as just another mouse, but unless you connect to it with PC1, then PC1 will not autoconnect to it, since it is now an unfamiliar device. 

If you do not change identity, and advertise with a whitelist/filter accept list, then it will just be a flag in the advertisement saying "I am only accepting connections from known devices". It doesn't specify what device it wants to connect to, so any whitelisted devices will be able to connect to it (at least for a short while at the time). 

Best regards,

Edvin

[DX_HK]

Thank you for your response.
In short, I didn't do enough research.
I checked again and it appears that the ID is always the same, and that unintended connections are avoided by only connecting with paired devices via directed advertising.

There's still a lot I don't know, so if there's something I don't understand, I'll ask.