bobzilladev
commented
1 year ago This data is rare enough that local collection or central aggregation of this data isn’t going to be priority for the project. This ticket will be left open in case someone in the community would like to take on the first step of adding local collection of this data to the app. Its implementation might be included as part of this other UUID issue.
I am submitted this request for completeness. There is also a UUID32-type advertisement, types 3 and 4 in https://bitbucket.org/bluetooth-SIG/public/src/main/assigned_numbers/core/ad_types.yaml. These can only be interpreted as the XXXXXXXX portion of the assigned base UUID
XXXXXXXX-0000-1000-8000-00805f9b34fb.In my dataset this type is very uncommon (e.g. if UUID16s is ~300k, this is ~2k datapoints in my data). However, again the interest is just in learning what I don't know may be out there currently, and thus the crowdsourced collection of WiGLE may turn up interesting data if this were being collected globally, since BT devices exhibit significant regionality in distribution (e.g. the device discussed here mostly shows up in Australia and Germany. And I had to cut it from my talk for time, but I've seen one particular device that exists primarily in Maryland, and then doesn't exist at all in neighboring DC or Virginia, according to the WiGLE data (I think it has to do with the MD Lottery...still trying to figure it out))