Matter Over Thread pairing

Wuou commented 3 weeks ago

Hello, may I ask if the Matter Over Thread device can be paired using the Thread border route of the third party without using Apple Hub?

below commented 3 weeks ago

This is precisely what this sample is for. If you are using Apple HomeKit, all of this is unnecessary.

Wuou commented 3 weeks ago

This is precisely what this sample is for. If you are using Apple HomeKit, all of this is unnecessary.

Thank you for your answer. It was very helpful. I am using the ESP32 Thread border route, but the first step when pairing Thread devices gives an error. I'm still using the process of pairing with over wifi devices. I do not know whether the Thread device process is not the same. The device said that the Thread network information was wrong when pairing, but my APP didn't even go to the selectThreadNetwork step. So, does the APP need to set up ThreadNetwork first? It looks like this:

guard
        let extendedPANID = "DEAD00BEEF00CAFF".toHexData(),
              let mKey = "00112233445566778899aabbccddeeff".toHexData(),
        let pskc = "104810e2315100afd6bc9215a6bfac53".toHexData(),
        let panId = "1234".toHexData(),
        let bid = "b844475afeea169b7eed957464179127".toHexData() else { return }

        let tod = MTRThreadOperationalDataset(networkName: "OpenThread-ESP", extendedPANID: extendedPANID, masterKey: mKey, psKc: pskc, channelNumber: NSNumber(value: 25), panID: panId)
        guard let data = tod?.data() else { return }
        ThreadCredentialsManager.shared.saveThreadOperationalCredentials(activeOpsDataset: data, borderAgentId: bid) { flag in
            print("save  ->  \(flag) ")
        }

And then initiate matching:

Take the first step

var request = MatterAddDeviceRequest(topology: topology)
request.perform()

2, then get selectThreadNetwork callback information, set the thread network and Keychain new sharing code

Finally, match the Matter

guard let payload = try?  MTRSetupPayload(onboardingPayload: onboardingPayload) else {
completion(false)
return
}

try deviceController? .setupCommissioningSession(with: payload, newNodeID: commissioningDeviceID)

Wuou commented 3 weeks ago

This is precisely what this sample is for. If you are using Apple HomeKit, all of this is unnecessary.

On Android, enter the extendedPANID, masterKey, panID and other parameters before initiating the pairing

But iOS is different, there's no place to set these parameters initially, so I'm not sure if I'm doing it right

I did a lot of searching, but there was no detailed explanation, so I wonder if Apple has limited the use of the Home Hub to pair Thread devices. Can't the self-developed app use Matter and MatterSupport to complete the pairing of Thread devices Could you help me see it? Thank you very much

below commented 3 weeks ago

I did a lot of searching, but there was no detailed explanation There isn't much, as not many people are using this API

Can't the self-developed app use Matter and MatterSupport to complete the pairing of Thread devices

Of course it can. Step one: Do you have the com.apple.developer.networking.manage-thread-network-credentials entitlement?

Wuou commented 3 weeks ago

I did a lot of searching, but there was no detailed explanation There isn't much, as not many people are using this API

Can't the self-developed app use Matter and MatterSupport to complete the pairing of Thread devices

Of course it can. Step one: Do you have the com.apple.developer.networking.manage-thread-network-credentials entitlement?

Yes, I've added com.apple.developer.networking.manage-thread-network-credentials permissions. ThreadNetwork profiles are installed on both phones and mac. When I call storeCredentials (forBorderAgent: activeOperationalDataSet:), tip error "Couldn 't communicate with a helper application."

below commented 3 weeks ago

One tip I can give you: Your THClient should not be allocated locally but should live long enough for the operation to finish.

I am pulling the borderAgent ID out of the xa key out of the TXTRecord for the router, and the active Operational Data Set from the TBR itself.

Wuou commented 3 weeks ago

One tip I can give you: Your THClient should not be allocated locally but should live long enough for the operation to finish.

I am pulling the borderAgent ID out of the xa key out of the TXTRecord for the router, and the active Operational Data Set from the TBR itself.

I'm a little confused about THClient should not be allocated locally but should live long enough for the operation to finish. What should I do specifically?

I have tried before, through the tool DNSServerBrowser can get TXTRecord, but I do not know how to use this information, how should it be used in the Thread pairing process?

below commented 3 weeks ago

A call like this: THClient().storeCredentials(forBorderAgent:activeOperationalDataSet:) will fail. You need to assign THClient() to a variable that lives long enough for the callback to be executed.

        const char * xaKey = "xa";
        NSData * xa = nil;
        if (TXTRecordContainsKey(txtLen, txtRecord, xaKey)) {
            uint8_t valueLen;
            const void * valueStore = TXTRecordGetValuePtr(txtLen, txtRecord, xaKey, &valueLen);
            if (valueStore != nil) {
                xa = [NSData dataWithBytes:valueStore length:valueLen];
            }
        }