Activelook-API-Documentation icon indicating copy to clipboard operation
Activelook-API-Documentation copied to clipboard

Feedback on documentation

Open toncho11 opened this issue 8 months ago • 2 comments

I have worked on the integration of ENGO smart glasses with ESP32 and I noted a few things related to the documentation:

  1. Here I have a bit of a confusion. I am using these 16 bit UUIDs:

static BLEUUID GenericAccess_DeviceNameUUID((uint16_t)0x2a00); static BLEUUID GenericAccess_AppearanceUUID((uint16_t)0x2a01); static BLEUUID GenericAccess_PeripheralUUID((uint16_t)0x2A04);

instead of these 128 bit UUIDs as stated in the documentation:

00002A00-0000-1000-8000-00805F9B34FB 00002A01-0000-1000-8000-00805F9B34FB 00002A04-0000-1000-8000-00805F9B34FB

The 128 bit versions do not work, only the 16 bit do work. In general the BLE library for ESP32 that I am using can handle both 16 and 128 bit UUIDs and it works. So I am a bit confused.

  1. The "0783b03e-8535-b5a0-7140-a304d2495cb7" UUID (ActiveLook® Commands Interface) in the documenation has a "0x" in front of it. I think this is not consistent with a policy where the 16 bit UUIDs do have "0x" and the 128 bit do not have.

toncho11 avatar Oct 09 '23 11:10 toncho11