• OK, so if I understand straight:

    • Customer buys BLE tag or some other small device, say a keyring fob
    • Customer downloads your app, or uses your webpage, then hits the "register device" button and registers their BLE device with your service.
      • (your service maintains a database of UUIDs of bluetooth devices associated with customers)
    • Customer enters store with their BLE device
    • POS automatically detects it and loads up their details.

    Are you making your own BLE devices? If so, then a way around the randomization of the UUID would be to expose your own GATT service on the device which exposes a persistent ID, and use that instead of the UUID. Then you could easily use WebBLE to do the registration with no further modification (this is what is suggested in the spec).


Avatar for daphtdazz @daphtdazz started