HID keyboard. Connection termination for power budgeting

[Valer_I]

Hello, I'm trying to optimize power on HID Keyboard app. This post was helpfull but yet some questions remains.
If I use several services, and want central to be abble to connect the peripheral in usage one of them is required. In real as soon as peripheral start advertising, the central's HID driver connects device in a very fast intervals (HID over GATT Profile Specification "5.2.6 Fast Connection Interval ...7.5 ms - 50 ms") that is not power efficient.

I'd like to know whether is possible to advertise but not be connected by HID driver on central until keyboard event appear?

[Sigurd]

Hi,

Is there any reason to advertise if you don’t want the HID host to connect? (or don’t have data to send to the host). Advertising for no reason is not power efficient. If you have disconnected from the host due to inactivity and a key-press is registered (pending notification), first then should you start the advertisement (device-initiated connection procedure see section 5.1.3 in the specification).

[Valer_I]

Hello, the use case is:

• device combines two services
• device has two bonds saved and whitelist adverise using them.
• after keyboard activity on one bond device will disconnect. The other bonded peer central that do not use HID Keyboard, but use other service need to establish connection after device appeared in range of scanning.