New 'Indoor Positioning Service' and error value 0x80

RE: New 'Indoor Positioning Service' and error value 0x80

Hung Bui — Wed, 27 May 2015 14:24:56 GMT

@Mahendra: We use "authorize" because it's name of one of the characteristic's pemissions defined in spec. The purpose of write with authorization maybe not only just to validate if the value is correct but also if the central device is allowed to write, etc.

If the answer from RK helped, could you please check the answer as correct ?

RE: New 'Indoor Positioning Service' and error value 0x80

Mahendra Tailor — Wed, 27 May 2015 11:42:04 GMT

My bad. You are correct it will work. And beauty is that it can be enabled for only characteristics that you want via the metadata stuff. However, I hope Nordic duplicate the event+reply and replace 'authorize' with 'validate' purely from documentation point of view. Thank you very much for the suggestion

RE: New 'Indoor Positioning Service' and error value 0x80

RK — Wed, 27 May 2015 10:22:09 GMT

I don't understand what you mean by 'the nrferror would need to be translated in the stack into an att_err'. One of the parameters to that call includes a gatt_status code which indicates success or failure and maps to the ATT error codes defined by Bluetooth. If you set one of the defined constants, the correct ATT error is sent back to the host.

I don't see what else is needed here, perhaps you can explain.

RE: New 'Indoor Positioning Service' and error value 0x80

Mahendra Tailor — Wed, 27 May 2015 10:05:33 GMT

Interesting.

That can work as it provides the data to validate and the nrferror would need to be translated in the stack into an att_err.

The positive take on this is that the mechanism already exists so perhaps Nordic needs to create a specific event and reply function that deals with this.

I am encouraged. Thank you for the suggestion.

RE: New 'Indoor Positioning Service' and error value 0x80

RK — Wed, 27 May 2015 09:56:17 GMT

Does

sd_ble_gatts_rw_authorize_reply()

not do what you require? Make the parameter rw_auth and you'll get called on write and can reject with any GATT status code.