Hello, I make a matter matter device with Onoff function. I add the mode select cluster in device to set work mode of device. I can not find the work mode in Apple Home application, only the onoff switch shows in UI. I tested my device with chip-tool, and read out the mode from device. B.R. Joe

Hello, apparently, HMAccessorySetupManager.performMatterEcosystemAccessorySetup has been removed from HMAccessorySetupManager.h. Is there any more information on this? Has it moved to a different Framework, or has this kind of functionality ("setting up Matter accessories with a Matter Partner Ecosystem App") been removed from iOS?

Hi, Was anybody able to connect Matter device with iOS 16 phone? I've tried ESP32 board with m5stack. The ESP32 device was in commissioning mode, but Apple Home app was not recognising it (neither by QR code nor as nearby device).

In the Xcode 14 Release candidate, I get a No such module 'Matter' error when attempting to import Matter. Has Matter been removed from the iOS 16 RC? What are my options other than waiting for an iOS 16.1 Beta?

Hi, The WWDC2021 Video Add support for Matter in your smart home app has a bunch of code examples referencing APIs that are no longer present or deprecated, e.g. this one. Unfortunately the documentation doesn't give any hint on the replacement APIs. Most of them are to be found in HMMatter* objects. But in the video at 14:27 an API for CHIPDeviceController is shown. Unfortunately that one cannot be found anymore. Does anybody know how to achieve the described task (managing state and control of a matter accessory)

I'm looking for a tutorial or documentation on HMMatterRequestHandler. I'm aware of the brief mentions in wwdc21-10298 but it's not sufficient. Is there any tutorial/ more extensive documentation?

I'm trying to commission a matter device via HMAccessorySetupRequest.performMatterEcosystemAccessorySetup. After scanning the QR code via the system provided UI the app shows a system popup: Additional Setup Required This accessory required additional setup. Refer to the manufacturer's guide for more information Unfortunately there's no further information. Did anybody succeed in using this API and could assist?

Hi, I commissioned an ESP32C3 device running Matter using the Home app. The iPhone is on iOS version 16 beta 2. For this I used the all-clusters-app/esp32 example from the connectedhomeip repo. Commit ID for connectedhomeip: cfc35951be66a664a6efdadea56d1b8ea6e63e96 I cannot on the accessory screen see any option to create matter groups. Is there any such option available on the home app? Thanks, Ajay Gantayet

iOS version : 15.4.1 xcode : 13.3.1 my code: let threadClient = THClient() threadClient.retrieveAllCredentials { credentials, error in if let credentials = credentials { print(" count = \(credentials.count)") credentials.forEach { credential in print(" networkKey = \(String(describing: credential.networkKey))") print(" extendedPANID = \(String(describing: credential.extendedPANID))") print(" borderAgentID = \(String(describing: credential.borderAgentID))") print(" activeOperationalDataSet = \(String(describing: credential.activeOperationalDataSet))") print(" networkKey = \(String(describing: credential.networkKey))") print(" pskc = \(String(describing: credential.pskc))") print(" channel = \(credential.channel)") print(" panID = \(String(describing: credential.panID))") print(" creationDate = \(String(describing: credential.creationDate))") print(" lastModificationDate = \(String(describing: credential.lastModificationDate))") } } } result: 2022-05-09 18:04:29.864501+0900 [36766:2122724] Client: -[THClient connectToXPCService] - connectToXPCService Connection resumed 2022-05-09 18:04:29.867340+0900 [36766:2124576] Successfully established connection 2022-05-09 18:04:29.867367+0900 [36766:2124545] CTCS XPC Client - isConnected: true 2022-05-09 18:04:29.867434+0900 [36766:2124576] clientProxyWithErrorHandler connected=YES 2022-05-09 18:04:29.867540+0900 [36766:2124576] Client: -[THClient getConnectionEntitlementValidity]_block_invoke_2 - Error: (null) 2022-05-09 18:04:29.867628+0900 [36766:2122724] Client: -[THClient init] - XPC Client Init done 2022-05-09 18:04:29.867709+0900 [36766:2122724] Client: -[THClient retrieveAllCredentials:]:554 - Calling Server remoteObjectProxyWithErrorHandler 2022-05-09 18:04:29.867827+0900 [36766:2122724] -[THClient dealloc] : Client: - deallocated... 2022-05-09 18:04:29.867993+0900 [36766:2124576] Client: -[THClient retrieveAllCredentials:]_block_invoke - Error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service with pid 36689 named com.apple.ThreadNetwork.xpc was invalidated from this process." UserInfo={NSDebugDescription=The connection to service with pid 36689 named com.apple.ThreadNetwork.xpc was invalidated from this process.} The results are the same with retrievePreferredCredentials 2022-05-09 17:51:44.152819+0900 [36628:2119289] CTCS XPC Client - isConnected: true 2022-05-09 17:51:44.152987+0900 [36628:2118644] clientProxyWithErrorHandler connected=YES 2022-05-09 17:51:44.153174+0900 [36628:2118644] Client: -[THClient getConnectionEntitlementValidity]_block_invoke_2 - Error: (null) 2022-05-09 17:51:44.153328+0900 [36628:2114499] Client: -[THClient init] - XPC Client Init done 2022-05-09 17:51:44.153475+0900 [36628:2114499] Client: -[THClient retrievePreferredCredentials:]:636 - Calling Server remoteObjectProxyWithErrorHandler 2022-05-09 17:51:44.153660+0900 [36628:2114499] Client: -[THClient retrieveAllCredentials:]:554 - Calling Server remoteObjectProxyWithErrorHandler 2022-05-09 17:51:44.153821+0900 [36628:2114499] -[THClient dealloc] : Client: - deallocated... 2022-05-09 17:51:44.154 [com.apple.main-thread:2114499] I EasySetupSelectLocationRoomWireFrame(89):setInterface(presenter:resourceModel:device:) - setInterface() 2022-05-09 17:51:44.154977+0900 [36628:2119289] Client: -[THClient retrieveAllCredentials:]_block_invoke - Error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service with pid 36689 named com.apple.ThreadNetwork.xpc was invalidated from this process." UserInfo={NSDebugDescription=The connection to service with pid 36689 named com.apple.ThreadNetwork.xpc was invalidated from this process.} 2022-05-09 17:51:44.155242+0900 [36628:2119289] Client: -[THClient retrievePreferredCredentials:]_block_invoke - Error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service with pid 36689 named com.apple.ThreadNetwork.xpc was invalidated from this process." UserInfo={NSDebugDescription=The connection to service with pid 36689 named com.apple.ThreadNetwork.xpc was invalidated from this process.} of course entitlement Additional Capabilities are added. What does the error means? Is there any I am missing? DNS-SD monitoring status : Lookup MyHome8._meshcop._udp.local DATE: ---Mon 09 May 2022--- 13:49:49.712 ...STARTING... 15:05:07.265 MyHome8._meshcop._udp.local. can be reached at 20F.local.:49191 (interface 13)  rv=1 nn=MyHome8 xp=42?˟uJ? tv=1.2.0 vn=Apple\ Inc. xa=?\(s?\(?.? sb=\\\x00\\\x00\\\x001

Calling setupManager.addAndSetUpAccessories(for: topology) [CHIPAccessoryServer] CHIP Accessory pairing failed before network provisioning: Error Domain=CHIPErrorDomain Code=1 "Undefined error:50." UserInfo={NSLocalizedDescription=Undefined error:50.} I tested using https://github.com/project-chip/connectedhomeip Test Event 5 and Test Event 7, both fail.

Symbol not found: OBJC_CLASS$_HMCHIPServiceHome Expected in: /System/Library/Frameworks/HomeKit.framework/HomeKit HMCHIPServiceHome(uuid: UUID(), name: "Scott's") works fine in iOS 15.0 but all of the 15.1 betas (1,2,3,4) have had this issue preventing initializing home structures.

We're trying Matter devices on HomeKit but currently using ESP32 DevKits except the M5Stack. It wasn't really mentioned in the Enabling Matter PDF that only the M5Stack is supported but there's a preference for it for testing? I have tried building the firmware for an ESP32-DevKit and I keep getting 'Unsupported setup code' despite tweaking the vendor and product id. Haven't checked the code yet if there's just M5Stack specific code support for HomeKit provisioning but throwing this question either way here.