Absolute minimum discovery

[keith v]

Hi new to Bluetooth, but familiar with Radios and embedded devices

I have 2 devices that only connect to each other. in the interest of extreme battery conservation I need to reduce discovery to a minimum.

Device one is a remote, the central Device two is the peripheral that the remote controls. It will have attributes that the remote will set It will have attributes that the remote will read The attributes will never change except via a firmware upgrade, if they do it's OK if the remote doesn't work with the old versions

The first time pairing can be longer as it should only happen once.

BUT, once paired and Bonded, I need to be able to connect and send a attribute from the remote to the peripheral as fast as possible. I'd like to be able to do this in reaction to a button press on the remote.

1. The remote is sleeping and not connected ( but is bonded ?)
2. User presses a button
3. device wakes up, connects, sends message and returns to sleep

I'm hoping I can just use the UUID since I'm bonded? Can I just wait for an advertising packet and send the button press in the ack response?

TIA Keith

[RK]

This is increasingly a great idea and now the peripheral+central softdevice is becoming standard it's quite possible to make something which is both, a 'normal' peripheral for being connected to by smart centrals and a central to listen out for this kind of event from a simple device, like a remote.

You can get some kind of feedback, if you make the advertising scannable you'll get scanned and will receive the scan event report, when you get that, you at least know your advertisement was received and who received it.

I've been avoiding adding that complexity into my current design, and only just moved up to the S130/S132 anyway .. I think it's time for me to implement something like this, the current way I'm doing it does have noticeable lag sometimes.