Post

Replies

Boosts

Views

Activity

Reply to Matter commissioning issue with Matter support extension
@DTS Engineer Add in the log details for HomeService. 10:51:34.065680+0800 HomeUIService [A4B23DBC] Could not find CHIP setup payload string in response payload (null): Error Domain=HMErrorDomain Code=2 "(null)" 10:51:34.066071+0800 HomeUIService -[HSSetupStateMachineConfiguration setPairingError:] *** Setting pairingError *** = Error Domain=HMErrorDomain Code=2 "(null)" 10:51:34.066205+0800 HomeUIService pairStagedCHIPAccessoryToPartnerAppHome succeeded. 10:51:34.067111+0800 HomeUIService Calculating potential skip of: Error 10:51:34.067526+0800 HomeUIService Show step: Error 10:51:34.066587+0800 HomeUIService HSProximityCardHostViewController 318 -[HSProximityCardHostViewController coordinator:updatedConfiguration:]: Pairing 10:51:34.067718+0800 HomeUIService HSProxCardCoordinator tuple 0x5ca2373f0 accessory (null) nextViewController Pairing->Error 10:51:34.067900+0800 HomeUIService Presenting error card with error Error Domain=HMErrorDomain Code=2 "(null)" 10:51:34.067085+0800 HomeUIService Calculating potential skip of: Error 10:51:34.067501+0800 HomeUIService Show step: Error 10:51:34.067684+0800 HomeUIService HSProxCardCoordinator tuple 0x5ca2373f0 accessory (null) nextViewController Pairing->Error 10:51:34.068703+0800homed Exiting state Opening Pairing Window With Passcode - Failed that hasn't been entered 10:51:34.071873+0800 HomeUIService Presenting error screen w/ title Unable to Add Accessory, subtitle You may need to restart your accessory before you can add it to your home., pairing error Error Domain=HMErrorDomain Code=2 "(null)", underlyingError (null), errorLocalizedDescription You may need to restart your accessory before you can add it to your home.
Topic: App & System Services SubTopic: Core OS Tags:
Dec ’25
Reply to Matter commissioning issue with Matter support extension
@DTS Engineer Hi, we may have uploaded the incorrect logs. Please ignore FB17357284 and FB17357284. The issue we encountered is not "iOS not having thread credentials", but a problem with MatterSupport, which falls into the following two categories: 1.MatterSupport added the device successfully, but the "open commissioning window" command failed to launch. -----(case 1 error log)------ 10:51:34.061975+0800 homed Failed to open pairing window on the device. Status src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout -----(case 1 error log)------ 2.MatterSupport added the device successfully, but it didn’t send the "open commissioning window" command. -----(case 2.1 error log)------ 12:06:41.439907+0800 homed Commissioning complete for node ID 0x000000000D0503BA: success 12:06:41.442096+0800 homed <MTRDeviceController_Concrete: 0xc2cba0700, uuid: 654DB965-CD9A-48CE-8B8F-4CDFDB88A682, suspended: NO> 1 delegates called for -[MTRDeviceController controller:commissioningComplete:nodeID:metrics:] 12:06:41.767618+0800 homed [188914BD-5163-425C-9E59-CAE9BFA1A288] Could not find system commissioner pairing for newly staged server with identifier in all pairings: 2:06:41.767729+0800 homed Answering incoming message HMASC.m.confirmDeviceCredential (450D3439-6D1C-4F2B-AE19-B93901ECA5AF) from client 'HomeUIService' that expects a response with error Error Domain=HMErrorDomain Code=2 "(null)" 12:06:41.767868+0800 homed [188914BD-5163-425C-9E59-CAE9BFA1A288] tag="stagedPairingFailure" desc="Could not find system commissioner pairing for newly staged server" errorDomain="HMErrorDomain" errorCode="2" -----(case 2.1 error log)------ -----(case 2.2 error log)------ 08:34:18.679801+0800 homed [3713800559/1150757325(2684848347)] Failed to retrieve serial number: Error Domain=MTRInteractionErrorDomain Code=134 "The specified attribute or attribute data field or entry does not exist on the device." UserInfo={NSLocalizedDescription=The specified attribute or attribute data field or entry does not exist on the device.} 08:34:18.680480+0800 sharingd BLE Prox changed SFBLEDevice ID bb003d3c-ddca-1000-8000-001ff3fb80df, RSSI -74 (0)t~U, Ch 39, AdvD <4c000711063f0a0847cf1f9f9247d3ae971fc6a541>, ST AccessoryStatus, Nm 'BBUbpClM', Paired no, Cnx no, OBC=? 08:34:18.680768+0800 homed [3713800559/1150757325(2684848347)] Failed to fetch serial number of CHIP Accessory with error Error Domain=MTRInteractionErrorDomain Code=134 "The specified attribute or attribute data field or entry does not exist on the device." UserInfo={NSLocalizedDescription=The specified attribute or attribute data field or entry does not exist on the device.} 08:34:18.900535+0800 homed Could not find home with CHIP fabric ID: 1150757325 -----(case 2.2 error log)------ @DTS Engineer Please refer to the image above. We trust that you have understood our issue: a failure in the intermediate process of MatterSupport has prevented our app from completing commissioning. We request your team to provide a "reOpen commissioning window" API to enable us to re-open the pairing window and retry the device addition process. Alternatively, please let us know if you have any better suggestions or solutions.
Topic: App & System Services SubTopic: Core OS Tags:
Dec ’25
Reply to Matter commissioning issue with Matter support extension
Sorry about that. The log I had before might've given you the wrong idea. Actually, the error we run into a lot is "Could not find system commissioner pairing for newly staged server with identifier 6f:d6:63:43:b5:b9 in all pairings:", not "Failed to open pairing window on the device". I have uploaded the log with the ID: FB17357284 Could you assist us in resolving this issue? Thank you.
Topic: App & System Services SubTopic: Core OS Tags:
Apr ’25
Reply to Matter commissioning issue with Matter support extension
Sometimes, it doesn't even send the "open pairing window" command. It just gives an error right away. Do you know why that is? 错误 13:59:42.963124+0800 homed Mdns: Resolve failure (src/platform/Darwin/DnssdImpl.cpp:697: CHIP Error 0x00000074: The operation has been cancelled) 错误 13:59:42.963193+0800 homed OperationalSessionSetup[1:0000000023C84E43]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout 错误 13:59:42.963254+0800 homed Creating NSError from src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout (context: (null))
Topic: App & System Services SubTopic: Core OS Tags:
Apr ’25
Reply to Matter commissioning issue with Matter support extension
Hello. I would appreciate it if you could kindly help to solve this problem. Thank you very much! I have already filled in the relevant information in the feedback assistant and uploaded the sysdiagnose file: -- FB17317942 please file a bug describing what happened --When using our app to scan the QR code for adding a Thermostat (Matter Over Thread), an error occurred, stating: "Unable to Add Accessory". what time the failure occurred --2025-4-22 16-17 GMT+8 What system versions have you tested with/seen this on? --iOS 18.4.1 Can you provide more details about what you're controller configuration you're testing with? What's the pairing device (the device you're using the pair UI on), is there a Home Hub, and device(s) are acting as the bridge to Thread? --We don't have a Home Hub. Instead, we're using our own Matter Controller, which is also a Thread Border Router, and our Thermostat that works with Matter Over Thread. What's the ratio of success/failure when pairing? --When the network's good, the success rate's really high. Nine out of ten attempts are successful, and there's just one failure. --When the network's bad, the success rate's really low. Nine out of ten attempts are failures, and there's only one success. Our software development environment: MacOS 15.3.2 Xcode 16.2 iOS 18.4 Dart 3.4.1 Flutter 3.22.1 Matter Controller(Matter1.3) Thermostat(Matter1.3)
Topic: App & System Services SubTopic: Core OS Tags:
Apr ’25
Reply to Matter commissioning issue with Matter support extension
I am a colleague of the original poster MarcoKhoo. I would like to supplement with the complete log of the issues we have encountered. Logs: 错误 11:03:30.791227+0800 homed [188914BD-5163-425C-9E59-CAE9BFA1A288] Could not find system commissioner pairing for newly staged server with identifier <private> in all pairings: <private> 默认 11:03:30.791335+0800 homed Answering incoming message HMASC.m.confirmDeviceCredential (602718BC-314B-4555-9D32-2874A9D6207F) from client 'HomeUIService' that expects a response with error Error Domain=HMErrorDomain Code=2 "(null)" 错误 11:03:30.791488+0800 homed [188914BD-5163-425C-9E59-CAE9BFA1A288] tag="stagedPairingFailure" desc="Could not find system commissioner pairing for newly staged server" errorDomain="HMErrorDomain" errorCode="2" 错误 11:03:30.791779+0800 HomeUIService [C27DF567] Failed to stage CHIP accessory pairing in steps: Error Domain=HMErrorDomain Code=2 错误 11:03:30.791920+0800 HomeUIService -[HSSetupStateMachineCHIPPartnerConfiguration stageCHIPAccessory]_block_invoke Failed to stage CHIP accessory: Error Domain=HMErrorDomain Code=2 默认 11:03:30.792021+0800 HomeUIService -[HSSetupStateMachineConfiguration setPairingError:] *** Setting pairingError *** = Error Domain=HMErrorDomain Code=2 默认 11:03:30.792114+0800 HomeUIService -[HSSetupStateMachineCHIPPartnerConfiguration setPhase:] old phase: PairingInProgress new phase: PermanentlyFailed 错误 11:03:30.792260+0800 HomeUIService Unexpected accessory <private> setup error Error Domain=HMErrorDomain Code=2 默认 11:03:30.793215+0800 HomeUIService Updating status title: "<private>" description: "<private>" 默认 11:03:30.793335+0800 HomeUIService stageCHIPAccessory hit error Error Domain=HMErrorDomain Code=2 默认 11:03:30.793417+0800 HomeUIService -[HSSetupStateMachineConfiguration setPairingError:] *** Setting pairingError *** = Error Domain=HMErrorDomain Code=2 默认 11:03:30.793627+0800 HomeUIService -[HSSetupStateMachineConfiguration setPairingError:] *** Setting pairingError *** = Error Domain=HMErrorDomain Code=2 UserInfo={HFErrorUserInfoOptionsKey=<private>} 默认 11:03:30.793715+0800 HomeUIService <private> 318 -[HSProximityCardHostViewController coordinator:updatedConfiguration:]: Pairing 默认 11:03:30.793790+0800 HomeUIService Calculating potential skip of: Error 默认 11:03:30.793850+0800 HomeUIService Show step: Error 默认 11:03:30.793931+0800 HomeUIService <private> tuple 0xd0c3c1a70 accessory (null) nextViewController Pairing->Error 默认 11:03:30.794018+0800 HomeUIService Presenting error card with error Error Domain=HMErrorDomain Code=2 UserInfo={HFErrorUserInfoOptionsKey=<private>} 默认 11:03:30.803741+0800 HomeUIService Presenting error screen w/ title <private>, subtitle <private>, pairing error Error Domain=HMErrorDomain Code=2 UserInfo={HFErrorUserInfoOptionsKey=<private>}, underlyingError (null), errorLocalizedDescription <private> 默认 11:03:30.803822+0800 HomeUIService Prox Card UI Transition -> Error | VC: <private> 默认 11:03:30.804111+0800 HomeUIService stagePairingFuture result length 0 默认 11:03:30.804227+0800 HomeUIService <private> 318 -[HSProximityCardHostViewController coordinator:updatedConfiguration:]: Error
Topic: App & System Services SubTopic: Core OS Tags:
Apr ’25