It depends on the algorithm how the UUID is generated.
There is probability of duplicates but it's extremely small.
Please check section Variants and versions and Random UUID probability of duplicates at Wikipeda
Unless you are sure the UUID generator implementation is from reliable source, please use one of implementations that are proven to be reliable.
1 of 1 people found this helpful
As what I guess on the Windows UUIDs - often the date (and time) are used as starting value for the number generator. So, generating an UUID should be quite free of conflicts (to have same UUID generated by two different developers or even you generate a new one later). As long as all people use the same tool and generator.
Yes, for BLE we should use and just use the official ITU site:
This makes sure: if everybody using it for BLE UUIDs - there might not be a conflict with using the same UUID.
Using something else, e.g.:
Does not guarantee that same starting value, same randomization is used (and you might use an already existing UUID). So, using other UUID tools for BLE can be very risky (not for you but for your clients using two different devices and having issues with same UUID in both).
I suggest, before creating new UUIDs, if you need one for a service, attribute, characteristic, value, data type ... etc. - check out if BLE has already a well defined UUID. If so, please use it.
If WICED Sense would follow this approach as well - it makes the life easier: if you provide a temperature sensor - use the official, well known temperature UUID: so, any App can figure out as "there is a temperature" and use it. An App will work on different devices (with different temperature sensors but provided as a temperature feature). It makes also your life easier if your App can be reused on other devices or on other projects.
This should be the first place to look for an existing, well defined UUID: