RE: Device name truncated (well is there a way to overcome)

JohnM — Wed, 15 Aug 2018 15:49:29 GMT

ok thanks, I've deleted the UUID Batt service (whithout loosing the functionnality of course):

Before:

static ble_uuid_t m_adv_uuids[] = {
{BLE_UUID_NUS_SERVICE, BLE_UUID_TYPE_BLE},
{BLE_UUID_BATTERY_SERVICE, BLE_UUID_TYPE_BLE}
};

Then:

static ble_uuid_t m_adv_uuids[] = {
{BLE_UUID_NUS_SERVICE, BLE_UUID_TYPE_BLE}
};

And my device is ok again.

John.

RE: Device name truncated (well is there a way to overcome)

Einar Thorsrud — Wed, 15 Aug 2018 06:18:59 GMT

Hi,

The device name in the advertising packet is shortened if there is no room for the full device name. A sniffer/scanner cannot display this data before it connects to the device as it has not been transmitted over air, so there is no way it can know. However, the peer can read the device name characteristic after a connection is made, which is why you see the full name after connecting.

There are a few things you can do to get the full device name without connecting:

Use less other data in the advertisement packet (for instance you can remove the battery service UUID from the advertising packet).
Use a scan response and put some of the advertising data there (either the device name or something else)