This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Identifying unprovisioned mesh device

I'm struggling with how to properly identify an unprovisioned mesh device. Basically when i scan for unprovisioned devices from my iOS app, I'd like for only our devices to show up, not any random mesh device. I'm still struggling to understand all the terminology, but if I understand everything correctly, I should be checking the `p_device_uri` set in `mesh_provisionee_prov_start` against the advertised data, or something. According to the mesh spec, it seems like this data is hashed using the salt function `s1`, which I think corresponds to `OpenSSLHelper.calculateSalt` in the iOS SDK. However, what I'm not understanding is which data to actually check against and how. So far, when I discover unprovisioned proxy nodes, I can do this:

func centralManager(_ central: CBCentralManager,
                        didDiscover peripheral: CBPeripheral,
                        advertisementData: [String: Any],
                        rssi RSSI: NSNumber) {

  if let serviceData = advertisementData[CBAdvertisementDataServiceDataKey] as! [CBUUID: NSData]? {
    let provisioningData = serviceData[MeshServiceProvisioningUUID]
    print("service data: \(provisioningData)")
  }

}

`provisioningData` contains some bytes of data, for me it returned `E754E3DAAFFDEE419AC6AD32896107A80000`, Which is 18bytes. The mesh spec seems to define the beacon format as follows:

But this comes out to 23 bytes, so it can't really match the format of the data I received.

It seems that the nRF Connect application is able to decipher at least some of this data, since it shows the device UUID in its scan view, but since the source of this app is not available I can't check against it.

Any help would be appreciated!

Parents
  • HI Jnicklas, 

    cant you identify your devices by looking at the 16-byte Device UUID field in the Unprovisioned Device beacon advertisment packet?,(see section 3.9.2 Unprovisioned Device beacon in the v1.0.1 spec)

    Best regards

    Bjørn 

  • Hi Bjørn,

    Thanks for the response :) From what I understand, the device UUID is unique per device, but what I'm trying to do is identify a "class" of devices, not a specific device. I'm building a product and an accompanying iOS app, when a client purchases the product and downloads the iOS app, I want only this specific product to show up in the provisionable list, but I obviously don't know which exact device they have purchased, if that makes sense?

    Section 3.9.1 is exactly the part of the mesh spec that I screenshotet in my original question, where the unprovisioned device beacon comes out to 23 bytes according to the layout given in the screenshot. What I haven't been able to figure out is how to extract this information in iOS, and then how to use this infromation to identify a class of devices.

    All the best,

    /Jonas

Reply
  • Hi Bjørn,

    Thanks for the response :) From what I understand, the device UUID is unique per device, but what I'm trying to do is identify a "class" of devices, not a specific device. I'm building a product and an accompanying iOS app, when a client purchases the product and downloads the iOS app, I want only this specific product to show up in the provisionable list, but I obviously don't know which exact device they have purchased, if that makes sense?

    Section 3.9.1 is exactly the part of the mesh spec that I screenshotet in my original question, where the unprovisioned device beacon comes out to 23 bytes according to the layout given in the screenshot. What I haven't been able to figure out is how to extract this information in iOS, and then how to use this infromation to identify a class of devices.

    All the best,

    /Jonas

Children
No Data
Related