this is NOT production ready, but this is a stab at decoding BT vendor IDs per #614 #615 . Android does some of the heavy lifting for us on mfgr ID cleanup, although it's unclear how reliable this is (and appears to be left to Android vendors?)
Open to feedback about how to do this in a way that would be suitable for production integration (and attendant efficient storage for the mfgr ID and service-uuids on device.)
NB: since MAC address randomization renders individual MACs alias-able, the primary key of any storage for these things would need to be a compound key of both MAC and date and or location.
Note that because the mfgr payloads contain information that serves as a fingerprint in some cases, we would never want to allow these payloads onto the server.
this is NOT production ready, but this is a stab at decoding BT vendor IDs per #614 #615 . Android does some of the heavy lifting for us on mfgr ID cleanup, although it's unclear how reliable this is (and appears to be left to Android vendors?) Open to feedback about how to do this in a way that would be suitable for production integration (and attendant efficient storage for the mfgr ID and service-uuids on device.)
NB: since MAC address randomization renders individual MACs alias-able, the primary key of any storage for these things would need to be a compound key of both MAC and date and or location.