You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My app is getting back the error status 0x0181 (385 decimal) in the BLE write callback when it tries to write to the FTMS's Fitness Machine Control Point characteristic 0x2AD9. Browsing the NimBLE code, I can't figure out what this status code means. The BLE device rejecting this write request is a ZwiftHub indoor bike trainer. No idea what BLE stack this device uses. Does anyone know?
The text was updated successfully, but these errors were encountered:
In Nimble error codes have ranges so that one can figure out from which layer error originated from.
0x181 is 0x100 + 0x81 which means it is ATT (0x100) error code with value 0x81.
0x81 is from ATT application error code range which means that its meaning is defined in FTMS specification.
For NimBLE neophytes (such as me) it would be helpful to have a comment with your clear explanation in the definition of the 'struct ble_gatt_error' inside ble_gatt.h.
My app is getting back the error status 0x0181 (385 decimal) in the BLE write callback when it tries to write to the FTMS's Fitness Machine Control Point characteristic 0x2AD9. Browsing the NimBLE code, I can't figure out what this status code means. The BLE device rejecting this write request is a ZwiftHub indoor bike trainer. No idea what BLE stack this device uses. Does anyone know?
The text was updated successfully, but these errors were encountered: