This would have to be unique to each individually built peripheral. I'm not sure that would be possible.
Maybe you can set an extra UUID characteristic in your peripherals or let it advertise an unique id in Manufacturer Data.
On Feb 8, 2013, at 9:20 PM, Darren Jones < email@hidden> wrote: Thanks Andras,
What would be the best method to remember a peripheral? In my case, I want to use a custom pairing method, so my app will only connect to peripherals that have been set up with that phone, and ignore others.
I have this working currently by remembering the UUID or each peripheral, however this is no good if they can change.
Thanks Surely yes! If the BT stack is reset, new UUIDs are generated. You should use the UUID as an opaque value. It should not have any meanining to your application and your app should always check the response of the system with operations that are concerned with UUIDs.
Regards, Andras
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
- Follow-Ups:
- Re: UUID
- From: Etan Kissling <email@hidden>
References: | |
| >UUID (From: Darren Jones <email@hidden>) |
| >Re: UUID (From: András Kövi <email@hidden>) |
| >Re: UUID (From: Darren Jones <email@hidden>) |
| >Re: UUID (From: Khaos Tian <email@hidden>) |
|