GAP Device Name vs Advertised Complete Local Name

RE: GAP Device Name vs Advertised Complete Local Name

WestCoastDaz — Sun, 05 Feb 2017 18:40:31 GMT

Petter,

Thanks for the clarification.

RE: GAP Device Name vs Advertised Complete Local Name

Petter Myhre — Fri, 03 Feb 2017 12:30:08 GMT

From CSS v7:

The Local Name data type shall be the same as, or a shortened version of, the local name assigned to the device. The Local Name data type value indicates if the name is complete or shortened. If the name is shortened, the complete name can be read using the remote name request procedure over BR/EDR or by reading the device name characteristic after the connection has been established using GATT.

So the local name shall be the same as the name in the device name characteristic.

RE: GAP Device Name vs Advertised Complete Local Name

Roger Clark — Fri, 03 Feb 2017 02:33:21 GMT

You could put the user defined name in the manufacturer data, or simply have a lookup table in your app.

I'm currently doing the latter, with my SmartBeacon, as it broadcasts its ID in the manufacturer data, and the user can select an unknown beacon, and assign it a name which is stored locally in the App So that next time the App detects the same ID it displays the name assigned by the user instead of the ID

This works OK as long as there is a one to one mapping between the SmartBeacon and the app, but if the same SmartBeacon needs to be used by multiple people, each one has to renter its name into their phone.

I'm debating adding a Characteristic that allows the name set in the app to be sent to the SmartBeacon which will then send that as part of its advertising, but this is a privacy issue as anyone could see the assigned name