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

[keith v]

Thanks for the replies. Yes both pieces have very limited power budgets, the peripheral the lowest power requirements, scanning would kill the battery pretty fast I think

There is 2 way communication, it's very small data but it is there. So it looks like, once it's bonded with the UUIDs stored, Its just a connect and go, no need to discover anything GATTs and stuff. That would be nice.

Security, dang I hope not, but probably.

Anyone want to guess what a connect time would be? under a second hopefully?

The accell sounds cool, but this may be put in a pocket and would be constantly be active!

Keith