I'm trying to find the UUID for the 'Time Second 32' characteristic described in the GSS v2 available here, but I can't find it in the Bluetooth Assigned Numbers document.
Is this normal and is it no longer available for some reason?
What gives?
I'm trying to find the UUID for the 'Time Second 32' characteristic described in the GSS v2 available here, but I can't find it in the Bluetooth Assigned Numbers document.
Is this normal and is it no longer available for some reason?
What gives?
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
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
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.