TX Power Level Bluetooth Characteristic

[sandeepmistry]

TX Power Level Bluetooth Characteristic

[linuxdevel]

If I'm not wrong, I can just add a characteristics according to https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=239393

Question is answered.. Feel free to delete the question.

[daviddedwin]

@sandeepmistry Not sure how this is done in the API, the nRF8001 ACI has the Broadcast/Connect/Bond all of which can be used to advertise data. The ACI command OpenAdvPipe is also used to load data from a Specific Characteristic into the advertising data. The Temperature broadcast example shows how to broadcast a Characteristic.

[sandeepmistry]

@linuxdevel do you want to advertise the TX power using GAP? (This is not supported).

@daviddedwin characteristics can be broadcasted in the GAP service data using the characteristic.broadcast() API. For more info see:

• https://github.com/sandeepmistry/arduino-BLEPeripheral/blob/master/API.md#broadcast
• EddystoneBeacon:
  • https://github.com/sandeepmistry/arduino-BLEPeripheral/blob/master/EddystoneBeacon.cpp#L34
  • https://github.com/sandeepmistry/arduino-BLEPeripheral/blob/master/EddystoneBeacon.cpp#L68

[linuxdevel]

@sandeepmistry I thought it was supported from what I see here : https://www.bluetooth.org/en-us/specification/assigned-numbers/generic-access-profile

0x0A «Tx Power Level» Bluetooth Core Specification:
Vol. 3, Part C, section 8.1.5 (v2.1 + EDR, 3.0 + HS and 4.0)
Vol. 3, Part C, sections 11.1.5 and 18.3 (v4.0)
Core Specification Supplement, Part A, section 1.5

[sandeepmistry]

@linuxdevel yep, it's part of the spec.

However, BLEPeripheral tries to keep things simple.

It only allows the following:

• Advertisement data: service UUID or Manufacturer data + service data for broadcasted characteristic (if there is space)
• Scan response data: local name

[sandeepmistry]

@linuxdevel I'm closing this for now.