Characteristic in Bluetooth GSS has no UUID in their 16-bit UUID Numbers Document

RE: Characteristic in Bluetooth GSS has no UUID in their 16-bit UUID Numbers Document

Simonr — Mon, 25 Jan 2021 11:16:46 GMT

Sorry about the late reply, but it took some time to find an answer to each question. No, there is not any documentation of which attributes do not have a UUID, but most of the Mesh models attributes are missing UUIDs. The only mesh models with UUIDs are the ones used for pre-existing characteristics.

I understand the confusion, and there is being work made to remedy this. Hopefully we'll see an update of the documentation sooner rather than later. Sorry about the lack of detals, but this is the information I have.

Best regards,

Simon

RE: Characteristic in Bluetooth GSS has no UUID in their 16-bit UUID Numbers Document

kalknight — Wed, 20 Jan 2021 01:30:28 GMT

Ok thank you. Is there a document that differentiates which attributes are only used in the Mesh models?

I was planning on using it in a custom service for time sync purposes (and also potentially overnight 'sleeping' of a sensor), hence the need for a uint32_t length time characteristic. It's not a make or break though and I'm considering other methods. I mostly just became very confused as to why it didn't have a UUID.

As a note, I'm aware that Nordic do not create the Bluetooth standards, but it would be useful for the GSS to include the UUID's with each characteristic that has one. I'm assuming this is by design but it's a bit annoying.

RE: Characteristic in Bluetooth GSS has no UUID in their 16-bit UUID Numbers Document

Simonr — Tue, 19 Jan 2021 13:43:39 GMT

I just got confirmation that this characteristic has not been assigned a UUID as of yet, as it is part of the Mesh 'characteristics' that got included in the GSS and are only used by Mesh models thus far which do not require UUIDs. This has been reported, and it will be assigned a UUID in the future.

Do you plan on using this characteristic for something specific, or did you ask out of curiosity?

Best regards,

Simon

RE: Characteristic in Bluetooth GSS has no UUID in their 16-bit UUID Numbers Document

Simonr — Tue, 19 Jan 2021 12:55:23 GMT

This was delayed a bit during the Holidays, as key staff were out of office, and I'm still waiting for a reply from the expert on the matter. What seems to be the case as of now is that the UUID is simply missing from the Assigned Numbers document, also in the latest revision as of 07.01.2021. I will update you when I know more. Thank you for your patience!

Best regards,

Simon

RE: Characteristic in Bluetooth GSS has no UUID in their 16-bit UUID Numbers Document

kalknight — Tue, 19 Jan 2021 02:31:51 GMT

Hi Simon,

Any news on this UUID?

RE: Characteristic in Bluetooth GSS has no UUID in their 16-bit UUID Numbers Document

Simonr — Thu, 17 Dec 2020 12:56:32 GMT

You're right, of course. Sorry about that! It does seem like this characteristic is missing from the UUID table altogether. Let me ask around internally if anyone can explain it. Otherwise it probably has to be reported to the Bluetooth SIG as a missing feature.

Best regards,

Simon

RE: Characteristic in Bluetooth GSS has no UUID in their 16-bit UUID Numbers Document

kalknight — Wed, 16 Dec 2020 23:42:02 GMT

Hi Simon,

Thank you for the reply and no worries if the next response takes a little longer.

The Time Second 32 is listed as a characteristic not a unit (if you go to section 3.197 Time Second 32 in the GSS V2 you'll see it).

There are two other similar characteristics that I was able to find the UUID in the document linked above: Time Second 8 & Time Second 16. I just don't know why Time Second 32 is missing from the UUID table?

RE: Characteristic in Bluetooth GSS has no UUID in their 16-bit UUID Numbers Document

Simonr — Wed, 16 Dec 2020 12:56:46 GMT

I think "Time Second 32" is not specifically described as "32" in the Assigned Numbers document, but is rather described as the time (second) unit. See picture below.

Best regards,

Simon

PS: The Holiday season is upon us, which will leave the Nordic support team understaffed until January 4th, 2021. This means that delayed replies will occur during this time. Sorry about the inconvenience and happy Holidays!