Matter is an IP-based, royalty-free connectivity protocol standard that enables communication among a wide range of smart devices.

Posts under Matter tag

134 Posts

Post

Replies

Boosts

Views

Activity

how to attribute bind with switch and bulb on home app
I can bind the light bulb to the light switch through chip-tool software But when I added the light bulb to the apple home app, I noticed two problems (1) The light switch is displayed as an unsupported accessory, note that it is an unsupported accessory, not an uncertified device, because the light bulb can be normally added to the home app and is only displayed as an uncertified device (2) If the light switch can be added to the home app, then I do not know how to bind the light bulb to the light switch
1
0
1.2k
Jul ’23
MatterSupport integrated with objective-c No MatterAddDeviceExtensionRequestHandler
Run the sample code as doc https://developer.apple.com/documentation/mattersupport?changes=latest_minor import MatterSupport let request = MatterAddDeviceRequest( topology: .init(ecosystemName: "Acme SmartHome", homes: [ .init(displayName: "Default Acme Home"), ]) ) do { try await request.perform() print("Successfully set up a device!") } catch { print("Failed to set up a device with error: \(error)") } it runs but stuck in the scene below, never get the callback. Another issue about MatterSupport, when integrated with objective-c the bridge file(eg xx-Swift.h) turn out to show error: Cannot find interface declaration for 'MatterAddDeviceExtensionRequestHandler', superclass of 'MatterAddDeviceHandler' Xcode Version 14.2 (14C18) My code: // // MatterHelper.swift // xx // // Created by Robin on 2023/3/21. // import Foundation import MatterSupport @available(iOS 16.1, *) class MatterHelper: NSObject { @objc class func commission() { let request = MatterAddDeviceRequest( topology: .init(ecosystemName: "RRRRRR", homes: [ .init(displayName: "R11111"), .init(displayName: "R222222") ]) ) Task.init { do { try await request.perform() print("Successfully set up a device!") } catch { print("Failed to set up a device with error: \(error)") } } } } @available(iOS 16.1, *) class MatterAddDeviceHandler: MatterAddDeviceExtensionRequestHandler { override func validateDeviceCredential(_ deviceCredential: MatterAddDeviceExtensionRequestHandler.DeviceCredential) async throws { print("validateDeviceCredential \(deviceCredential)") } override func selectThreadNetwork(from threadScanResults: [MatterAddDeviceExtensionRequestHandler.ThreadScanResult]) async throws -> MatterAddDeviceExtensionRequestHandler.ThreadNetworkAssociation { print("selectThreadNetwork \(threadScanResults)") return ThreadNetworkAssociation.defaultSystemNetwork } override func commissionDevice(in home: MatterAddDeviceRequest.Home?, onboardingPayload: String, commissioningID: UUID) async throws { print("Home: \(String(describing: home)) " + "payload: \(onboardingPayload) " + "commissionID: \(commissioningID)") } } Many thanks for your help.
3
0
1.7k
Jun ’23
How do I get the device ID from the callback information when a HomeKit paired with a Matter device within an application
I'm trying to pair the Matter by calling HomeKit from within our app, I can successfully pair and the matter device is discovered via bonjour, but after the HomeKit pairing success callback, I can't get a similar UUID or other identifier. I invoked HomeKit with the following code - (void)addAccessoriesWithCompletion:(void (^)(NSError * _Nullable))completion {     if(@available(iOS 15.4, *)) {         HMAccessorySetupRequest *setupRequest = [[HMAccessorySetupRequest alloc] init];         setupRequest.homeUniqueIdentifier = self.currentHome.uniqueIdentifier;         [self.setupManager performAccessorySetupUsingRequest:setupRequest completionHandler:^(HMAccessorySetupResult * _Nullable result, NSError * _Nullable error) {                    completion(error);         }];     }     else {         [self.currentHome addAndSetupAccessoriesWithCompletionHandler:completion];     } } - (HMAccessorySetupManager *)setupManager {     if (_setupManager == nil) {         _setupManager = [[HMAccessorySetupManager alloc] init];     }     return _setupManager; } HomeKit successfully added device delegate - (void)home:(HMHome *)home didAddAccessory:(HMAccessory *)accessory {     if (self.homeDidAddAccessoryBlock) {         self.homeDidAddAccessoryBlock(accessory);     }     accessory.delegate = self; } Multiple matter devices may be discovered through bonjour, and I need to know which matter device I just added in order to bind to our user system. So I need to get the device id from the HomeKit pairing success callback so I can filter the matter device. Or do we need to set something on our matter firmware?
3
0
3.7k
Jun ’23
How do I obtain the unique ID of a device and control the device after adding a device using MatterSupport.framework
I am trying to manage my Matter device using MatterSupport.Framework. Prior to this I was using the matter.Framework, and I added devices through the commissionDevice API, which has the ability to set DeviceId for Matter devices. I was then able to use deviceId to control my device (like setting switches, brightness, etc.). But due to some other issues, I had to add my device using the MatterAddDeviceRequest API in MatterSupport. I can't find a unique identifier for a device such as "deviceID" in the documentation. So I'm confused, how do I control my matter device after adding it via the MatterAddDeviceRequest API
3
0
1.3k
Jun ’23
Commissioning from the CHIPDeviceController of the iOS Matter Stack fails due to the Incorrect state
Hello. When I call MatterAddDeviceRequest API, it returns HMErrorDomain Code=18 "Pairing Failed" error. As I seeing the log, commissioning from the CHIPDeviceController of the iOS Matter Stack fails due to the Incorrect state. Here is the log: default 10:41:50.653975-0500 HomeUIService [d <private>] <PKHost:0x283e6b000> Beginning discovery for flags: 1024, point: com.apple.matter.support.extension.device-setup default 10:41:50.891778-0500 homed Setting thread operational dataset from parameters default 10:41:50.891926-0500 homed Setting attestation nonce to random value default 10:41:50.892235-0500 homed Setting CSR nonce to random value error 10:41:50.892287-0500 homed Commissioning already in progress - not restarting error 10:41:50.892648-0500 homed Error(../../../../../../../../Sources/CHIPFramework/connectedhomeip/src/controller/CHIPDeviceController.cpp:811: CHIP Error 0x00000003: Incorrect state): Failure while pairing the device error 10:41:50.892873-0500 homed [3262693301/1] Commissioning failed: Error Domain=MTRErrorDomain Code=6 "Invalid object state." UserInfo={NSLocalizedDescription=Invalid object state., underlyingError=<private>} error 10:41:50.892905-0500 homed [3262693301/1] CHIP Accessory pairing failed: Error Domain=MTRErrorDomain Code=6 "Invalid object state." UserInfo={NSLocalizedDescription=Invalid object state., underlyingError=<private>} error 10:41:50.892930-0500 homed [3262693301/1] Cleaning up state due to pairing failure connectedhomeip/src/controller/CHIPDeviceController.cpp : CHIP_ERROR DeviceCommissioner::Commission(NodeId remoteDeviceId) { … if (mCommissioningStage != CommissioningStage::kSecurePairing) { ChipLogError(Controller, "Commissioning already in progress - not restarting"); return CHIP_ERROR_INCORRECT_STATE; } Is there any update for this problem?
0
0
1.5k
Apr ’23
How to access HMAcessory to my sample application using matterNodeId
I have commissioned a matter accessory (ERF32) into the Homekit app, using an Apple controller (Homepod mini.) I am able to read the accessory using Homekit APIs for accessory in home.accessories.filter({ $0.matterNodeID != nil }) { print(accessory.matterNodeID) } 3. I am able to read matterNodeID Using Homekit API's, but i am not understanidng how we can see clusters in the HMAccessory. My question is Does homekit supports seeing the clusters? Can anyone provide me the sample application how we can do this.
0
0
603
Apr ’23
NWBrowser does not discover Meross (Matter device)
Hello, I think that I found a bug with NWBrowser and I'd like to ask you can fix this. Problem NWBrowser does not return the result to the app, while NetServiceBrowser returns. Problem occurs when using only Meross device, in other Matter device cases, both api works fine. Actually I want to get TXT Record from Meross, but failed with NWBrowser Steps Add Meross plug device (Matter, Wi-Fi device) to Apple Home app Turn On Pairing Mode of Meross device When I try to discover it with NWBrowser > it is NOT discovered (with NetServiceBrowser > it is discovered) Results When I use NWBrowser, I can't get any result from the handler. On the other hand, with NetServiceBrowser, I can get a result. When I capture the packets with WireShark, the packets are same on both cases Case1: with NWBrowser Case2: with NetServiceBrowser With same packets, Case1 does not return any result and Case2 returns results. I'm trying to attaching the WireShark capture file and iOS console logs, but it continuosly fails. Please let me know how I can send them. Code Her is my code. NWBrowser let bonjourWithTXT = NWBrowser.Descriptor.bonjourWithTXTRecord(type: "_matterc._udp.", domain: "local.") let params = NWParameters.init() self.nwBrowser = NWBrowser(for: bonjourWithTXT, using: params) self.nwBrowser?.browseResultsChangedHandler = { [weak self] results, changes in // Can not get any results here // } self.nwBrowser?.start(queue: .main) NetServiceBrowser self.bonjourBrowser = NetServiceBrowser() self.bonjourBrowser?.delegate = self self.bonjourBrowser?.searchForServices(ofType: "_matterc._udp.", inDomain: "local.") func netServiceBrowser(_ browser: NetServiceBrowser, didFind service: NetService, moreComing: Bool) { service.delegate = self service.resolve(withTimeout: resolutionTimeout) netService.insert(service) } func netServiceBrowser(_ browser: NetServiceBrowser, didRemove service: NetService, moreComing: Bool) { netServices.remove(service) } func netServiceDidResolveAddress(_ service: NetService) { // I can get found services here // }
1
0
1.4k
Apr ’23
Homepod as home hub
Hi, I recently purchased a Homepod Mini to assist my family in controlling Homekit devices, especially lights. But also to add matter support for future devices. After installing the Homepod everything seemed fine, until it took over as the home hub, our Apple TV 4K without matter support has been previously our home hub, devices worked flawlessly when the Apple TV was the hub. Most of our lights are made by IKEA and utilize the Zigbee standard, a well proven and robust smart home standard that has been nothing but flawless in our experience. The Dirigera hub that controls these devices retains full and fast control over the devices connected to it. Solely making this a Homekit and Home related issue. The Homepod Mini says that devices are offline, even though they are fully and without problem available in the Home app. This isn't a major problem, but the problems don't end here. Devices such as outlets and lights are displayed as double, thus as seperate entities where one is offline and another one is available. While shortcut buttons appear in the home view, even though they shouldn't (as this is automatically disabled and definetly have not been ordered to show up in the home view.). Sometimes devices are completely listed as offline. Another thing is that the control of the devices has become extremely slow in comparison to what they were like when the Apple TV was the hub. I've tried everything listed on Apple's support pages and instructions/forums. I've also contacted IKEA and consulted their instructions and support pages. I've tried all fixes and suggestions on Reddit and other online forums. To describe, I've reset and removed the Homepod multiple times from my Home and icloud. I've also tried to add the Homepod to another home, but as the device sits on the same Wi-Fi its reverted back to being the other home's hub even though not being part of that home. I've also tried to re-add all devices and removing the IKEA devices /integration from the home which had no effect and only caused a lot of unnecessary work. This is extremly concerning as all of these devices are running on a network, that extensively uses ethernet has the 1 gig fiber speeds, and state of the art Wi-Fi 6E routers. In addition the fact that the Homepod is marketed as a home hub and as a matter hub but clearly fails in achieving these things as could be expected from Apple and the previous great experiences had with the Apple TV. To further add, the IKEA Trådfri and Dirigera hub is supposed to specifically, is fully approved and supported to work with Homekit and matter (even though that doesn't matter that much in this case) and is a mass market home smart system. It's also clear that this is an issue that isn't isolated to my case but has been extensively discussed by other IKEA and Homekit users and has according to others been reported to both Apple and IKEA multiple times but they seem to have taken no action. After reading these posts, it seems like Apple isn't willing to let users choose a prefered home hub or disable the homepods functionality as a home hub. I really don't care how Apple might eventually fix this issue, but just do it as soon as possible as this really breaks the functionality of my smart home.
1
1
2.6k
Apr ’23
Is there a way to support matter from iOS11.0?
Is there a way to support matter from iOS11.0? In the CHIP Tool iOS Sample Commissioner App readme doc says: Requires building and running the app to a physical device on iOS >= 15.4. Does it mean that the sample app matter framework cannot support iOS < 15.4? I have just changed the sample project configuration mini deployment version to iOS 11.0, built and ran, soon the app crashed Found MatterSupport.h is still empty, use Matter.h instead? Starting with 16.1 you need to use MatterSupport. In Xcode 14.2 iOS16.2 Framework MatterSupport.h is empty, should I use Matter.h instead? iShot_2023-03-15_19 37 28
1
0
1.1k
Mar ’23
HomeKit Matter Device Battery Level
Hello there, After including the power source cluster with it's feature maps, the HomeKit is not showing the remaining battery level for the Matter devices, I'm able to read back the power source cluster with my chip-tool for linux. My Apple System Specifications are, Apple BR -> Homepod Mini running tvOS 16.3.2 Matter Controller -> iPhone13 running iOS 16.3.1 Thanks in Advance.
0
0
1.7k
Mar ’23
MatterSupport framework MatterAddDeviceRequest Fails
[MatterAddDeviceRequest] Local browse failed; unable to start an add device operation (error: -65555: NoAuth) Failed to set up a device with error: -65555: NoAuth Code I am using -        let request = MatterAddDeviceRequest(         topology: .init(ecosystemName: "Test Echo", homes: [           .init(displayName: "Test Home 1"),         ]), setupPayload: nil, showing: .allDevices       )       do {         try await request.perform()         print("Successfully set up a device!")       } catch {         print("Failed to set up a device with error: (error)")       }
1
0
858
Mar ’23
Matter documentation help
I'm interested to learn more about this documentation: https://developer.apple.com/apple-home/matter/ It contains a bunch of information and also some statements I'm curious about. e.g. this one: Matter accessories can be managed in the Settings app Is the document referring to the iOS Settings app? I cannot find Matter accessories in the Settings App. I'd also like to learn more about the APIs (which and how to use) this document is telling about. Is anybody able to help?
0
1
1k
Mar ’23
iOS 16.1 API for Matter ecosystem implementation
Hello everyone, We are trying to manage matter devices within an iOS application. What we want is managing a matter fabric shared with other applications (iOS, Android, linux, ...). I read both 'Matter' and 'MatterSupport' documentations but neither framework seems to fit our needs. In the 'MatterSupport' documentations there is mention of an application Matter ecosystem implementation. I first thought it referenced a fabric but the API only allows us to specify an ecosytemName (Whatever that means). So my question is: How can we add devices to our own fabric with an official API ? And if not, does anyone know if the feature will be available in the near future ? Thank you in advance.
3
0
1.9k
Mar ’23
[Matter] Add device failure to iOS system fabric
Hi, When I use MatterAddDeviceRequest api in MatterSupport, system pop-up shows Pairing failed error. Could you please look into this why it occurs? If you provide the solution, it would be great help for me to add Matter device. Thank you. This is console log. 2022-12-26 15:53:53.151 [matter:1320010] 🔵 [1672037633151] [2422:1320010] CHIP: [DIS] Browsing for: _matterc._udp,_L1880 2 2022-12-26 15:53:53.153 [matter:1320316] 🟢 [1672037633152] [2422:1320316] CHIP: [DIS] Mdns: OnBrowseAdd name: 76549AC95D2520BF, type: _matterc._udp., domain: local., interface: 13 3 2022-12-26 15:53:53.153 [matter:1320316] 🟢 [1672037633152] [2422:1320316] CHIP: [DIS] Resolve type=_matterc._udp name=76549AC95D2520BF interface=13 4 2022-12-26 15:53:53.154 [matter:1320271] 🟢 [1672037633153] [2422:1320271] CHIP: [DIS] Mdns : OnNewInterface hostname:E2A2EB59C4923697.local. fullname:76549AC95D2520BF._matterc._udp.local. interface: 13 port: 42005 TXT:" VP=65521+32774 SII=6000 SAI=500 T=0 D=1880 CM=2 PH=36 PI=" 5 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Mdns: OnNewAddress interface: 13 ip:fd49:f8b0:496b:1:a6de:22c7:52c7:f7 6 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Mdns: OnNewAddress interface: 0 ip:218.38.137.27 7 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Mdns: Resolve success on interface 0 8 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Discovered node: 9 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] IP Address #1: 218.38.137.27 10 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Mrp Interval idle: not present 11 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Mrp Interval active: not present 12 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] TCP Supported: 0 13 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Commissioning Mode: 0 14 2022-12-26 15:54:23.155 [matter:1320271] E 🔴 [1672037663154] [2422:1320271] CHIP: [CTL] Discovery timed out
0
1
1.2k
Feb ’23
HMErrorDomain code=76 always occurs when using MatterSupport api
Hi, I wanted to use MatterAddDeviceRequest api in MatterSupport. When I called api, system pop-up shows up and then right after tapping 'Add to @' button, pop-up always shows HMErrorDomain 76 error. I found this code in HomeKit.HMError case keychainSyncNotEnabled = 76 I wonder that enabling keychain sync is mandatory to use MatterAddDeviceRequest api? Or could you tell me why this error always occurs? Thanks!
2
1
2k
Jan ’23
What does this error mean, HAPErrorDomain Code = 3
I have tried to add Meross matter plug but still pairing failed, it reported always same error. error: related decl 'e' for HMErrorCode(_nsError: Error Domain=HMErrorDomain Code=18 "Pairing Failed" UserInfo={NSLocalizedDescription=Pairing Failed, NSUnderlyingError=0x281503cc0 {Error Domain=HAPErrorDomain Code=3 "(null)"}})
Replies
0
Boosts
0
Views
927
Activity
Jul ’23
how to attribute bind with switch and bulb on home app
I can bind the light bulb to the light switch through chip-tool software But when I added the light bulb to the apple home app, I noticed two problems (1) The light switch is displayed as an unsupported accessory, note that it is an unsupported accessory, not an uncertified device, because the light bulb can be normally added to the home app and is only displayed as an uncertified device (2) If the light switch can be added to the home app, then I do not know how to bind the light bulb to the light switch
Replies
1
Boosts
0
Views
1.2k
Activity
Jul ’23
MatterSupport integrated with objective-c No MatterAddDeviceExtensionRequestHandler
Run the sample code as doc https://developer.apple.com/documentation/mattersupport?changes=latest_minor import MatterSupport let request = MatterAddDeviceRequest( topology: .init(ecosystemName: "Acme SmartHome", homes: [ .init(displayName: "Default Acme Home"), ]) ) do { try await request.perform() print("Successfully set up a device!") } catch { print("Failed to set up a device with error: \(error)") } it runs but stuck in the scene below, never get the callback. Another issue about MatterSupport, when integrated with objective-c the bridge file(eg xx-Swift.h) turn out to show error: Cannot find interface declaration for 'MatterAddDeviceExtensionRequestHandler', superclass of 'MatterAddDeviceHandler' Xcode Version 14.2 (14C18) My code: // // MatterHelper.swift // xx // // Created by Robin on 2023/3/21. // import Foundation import MatterSupport @available(iOS 16.1, *) class MatterHelper: NSObject { @objc class func commission() { let request = MatterAddDeviceRequest( topology: .init(ecosystemName: "RRRRRR", homes: [ .init(displayName: "R11111"), .init(displayName: "R222222") ]) ) Task.init { do { try await request.perform() print("Successfully set up a device!") } catch { print("Failed to set up a device with error: \(error)") } } } } @available(iOS 16.1, *) class MatterAddDeviceHandler: MatterAddDeviceExtensionRequestHandler { override func validateDeviceCredential(_ deviceCredential: MatterAddDeviceExtensionRequestHandler.DeviceCredential) async throws { print("validateDeviceCredential \(deviceCredential)") } override func selectThreadNetwork(from threadScanResults: [MatterAddDeviceExtensionRequestHandler.ThreadScanResult]) async throws -> MatterAddDeviceExtensionRequestHandler.ThreadNetworkAssociation { print("selectThreadNetwork \(threadScanResults)") return ThreadNetworkAssociation.defaultSystemNetwork } override func commissionDevice(in home: MatterAddDeviceRequest.Home?, onboardingPayload: String, commissioningID: UUID) async throws { print("Home: \(String(describing: home)) " + "payload: \(onboardingPayload) " + "commissionID: \(commissioningID)") } } Many thanks for your help.
Replies
3
Boosts
0
Views
1.7k
Activity
Jun ’23
How do I get the device ID from the callback information when a HomeKit paired with a Matter device within an application
I'm trying to pair the Matter by calling HomeKit from within our app, I can successfully pair and the matter device is discovered via bonjour, but after the HomeKit pairing success callback, I can't get a similar UUID or other identifier. I invoked HomeKit with the following code - (void)addAccessoriesWithCompletion:(void (^)(NSError * _Nullable))completion {     if(@available(iOS 15.4, *)) {         HMAccessorySetupRequest *setupRequest = [[HMAccessorySetupRequest alloc] init];         setupRequest.homeUniqueIdentifier = self.currentHome.uniqueIdentifier;         [self.setupManager performAccessorySetupUsingRequest:setupRequest completionHandler:^(HMAccessorySetupResult * _Nullable result, NSError * _Nullable error) {                    completion(error);         }];     }     else {         [self.currentHome addAndSetupAccessoriesWithCompletionHandler:completion];     } } - (HMAccessorySetupManager *)setupManager {     if (_setupManager == nil) {         _setupManager = [[HMAccessorySetupManager alloc] init];     }     return _setupManager; } HomeKit successfully added device delegate - (void)home:(HMHome *)home didAddAccessory:(HMAccessory *)accessory {     if (self.homeDidAddAccessoryBlock) {         self.homeDidAddAccessoryBlock(accessory);     }     accessory.delegate = self; } Multiple matter devices may be discovered through bonjour, and I need to know which matter device I just added in order to bind to our user system. So I need to get the device id from the HomeKit pairing success callback so I can filter the matter device. Or do we need to set something on our matter firmware?
Replies
3
Boosts
0
Views
3.7k
Activity
Jun ’23
How do I obtain the unique ID of a device and control the device after adding a device using MatterSupport.framework
I am trying to manage my Matter device using MatterSupport.Framework. Prior to this I was using the matter.Framework, and I added devices through the commissionDevice API, which has the ability to set DeviceId for Matter devices. I was then able to use deviceId to control my device (like setting switches, brightness, etc.). But due to some other issues, I had to add my device using the MatterAddDeviceRequest API in MatterSupport. I can't find a unique identifier for a device such as "deviceID" in the documentation. So I'm confused, how do I control my matter device after adding it via the MatterAddDeviceRequest API
Replies
3
Boosts
0
Views
1.3k
Activity
Jun ’23
Commissioning from the CHIPDeviceController of the iOS Matter Stack fails due to the Incorrect state
Hello. When I call MatterAddDeviceRequest API, it returns HMErrorDomain Code=18 "Pairing Failed" error. As I seeing the log, commissioning from the CHIPDeviceController of the iOS Matter Stack fails due to the Incorrect state. Here is the log: default 10:41:50.653975-0500 HomeUIService [d <private>] <PKHost:0x283e6b000> Beginning discovery for flags: 1024, point: com.apple.matter.support.extension.device-setup default 10:41:50.891778-0500 homed Setting thread operational dataset from parameters default 10:41:50.891926-0500 homed Setting attestation nonce to random value default 10:41:50.892235-0500 homed Setting CSR nonce to random value error 10:41:50.892287-0500 homed Commissioning already in progress - not restarting error 10:41:50.892648-0500 homed Error(../../../../../../../../Sources/CHIPFramework/connectedhomeip/src/controller/CHIPDeviceController.cpp:811: CHIP Error 0x00000003: Incorrect state): Failure while pairing the device error 10:41:50.892873-0500 homed [3262693301/1] Commissioning failed: Error Domain=MTRErrorDomain Code=6 "Invalid object state." UserInfo={NSLocalizedDescription=Invalid object state., underlyingError=<private>} error 10:41:50.892905-0500 homed [3262693301/1] CHIP Accessory pairing failed: Error Domain=MTRErrorDomain Code=6 "Invalid object state." UserInfo={NSLocalizedDescription=Invalid object state., underlyingError=<private>} error 10:41:50.892930-0500 homed [3262693301/1] Cleaning up state due to pairing failure connectedhomeip/src/controller/CHIPDeviceController.cpp : CHIP_ERROR DeviceCommissioner::Commission(NodeId remoteDeviceId) { … if (mCommissioningStage != CommissioningStage::kSecurePairing) { ChipLogError(Controller, "Commissioning already in progress - not restarting"); return CHIP_ERROR_INCORRECT_STATE; } Is there any update for this problem?
Replies
0
Boosts
0
Views
1.5k
Activity
Apr ’23
How to access HMAcessory to my sample application using matterNodeId
I have commissioned a matter accessory (ERF32) into the Homekit app, using an Apple controller (Homepod mini.) I am able to read the accessory using Homekit APIs for accessory in home.accessories.filter({ $0.matterNodeID != nil }) { print(accessory.matterNodeID) } 3. I am able to read matterNodeID Using Homekit API's, but i am not understanidng how we can see clusters in the HMAccessory. My question is Does homekit supports seeing the clusters? Can anyone provide me the sample application how we can do this.
Replies
0
Boosts
0
Views
603
Activity
Apr ’23
NWBrowser does not discover Meross (Matter device)
Hello, I think that I found a bug with NWBrowser and I'd like to ask you can fix this. Problem NWBrowser does not return the result to the app, while NetServiceBrowser returns. Problem occurs when using only Meross device, in other Matter device cases, both api works fine. Actually I want to get TXT Record from Meross, but failed with NWBrowser Steps Add Meross plug device (Matter, Wi-Fi device) to Apple Home app Turn On Pairing Mode of Meross device When I try to discover it with NWBrowser > it is NOT discovered (with NetServiceBrowser > it is discovered) Results When I use NWBrowser, I can't get any result from the handler. On the other hand, with NetServiceBrowser, I can get a result. When I capture the packets with WireShark, the packets are same on both cases Case1: with NWBrowser Case2: with NetServiceBrowser With same packets, Case1 does not return any result and Case2 returns results. I'm trying to attaching the WireShark capture file and iOS console logs, but it continuosly fails. Please let me know how I can send them. Code Her is my code. NWBrowser let bonjourWithTXT = NWBrowser.Descriptor.bonjourWithTXTRecord(type: "_matterc._udp.", domain: "local.") let params = NWParameters.init() self.nwBrowser = NWBrowser(for: bonjourWithTXT, using: params) self.nwBrowser?.browseResultsChangedHandler = { [weak self] results, changes in // Can not get any results here // } self.nwBrowser?.start(queue: .main) NetServiceBrowser self.bonjourBrowser = NetServiceBrowser() self.bonjourBrowser?.delegate = self self.bonjourBrowser?.searchForServices(ofType: "_matterc._udp.", inDomain: "local.") func netServiceBrowser(_ browser: NetServiceBrowser, didFind service: NetService, moreComing: Bool) { service.delegate = self service.resolve(withTimeout: resolutionTimeout) netService.insert(service) } func netServiceBrowser(_ browser: NetServiceBrowser, didRemove service: NetService, moreComing: Bool) { netServices.remove(service) } func netServiceDidResolveAddress(_ service: NetService) { // I can get found services here // }
Replies
1
Boosts
0
Views
1.4k
Activity
Apr ’23
Homepod as home hub
Hi, I recently purchased a Homepod Mini to assist my family in controlling Homekit devices, especially lights. But also to add matter support for future devices. After installing the Homepod everything seemed fine, until it took over as the home hub, our Apple TV 4K without matter support has been previously our home hub, devices worked flawlessly when the Apple TV was the hub. Most of our lights are made by IKEA and utilize the Zigbee standard, a well proven and robust smart home standard that has been nothing but flawless in our experience. The Dirigera hub that controls these devices retains full and fast control over the devices connected to it. Solely making this a Homekit and Home related issue. The Homepod Mini says that devices are offline, even though they are fully and without problem available in the Home app. This isn't a major problem, but the problems don't end here. Devices such as outlets and lights are displayed as double, thus as seperate entities where one is offline and another one is available. While shortcut buttons appear in the home view, even though they shouldn't (as this is automatically disabled and definetly have not been ordered to show up in the home view.). Sometimes devices are completely listed as offline. Another thing is that the control of the devices has become extremely slow in comparison to what they were like when the Apple TV was the hub. I've tried everything listed on Apple's support pages and instructions/forums. I've also contacted IKEA and consulted their instructions and support pages. I've tried all fixes and suggestions on Reddit and other online forums. To describe, I've reset and removed the Homepod multiple times from my Home and icloud. I've also tried to add the Homepod to another home, but as the device sits on the same Wi-Fi its reverted back to being the other home's hub even though not being part of that home. I've also tried to re-add all devices and removing the IKEA devices /integration from the home which had no effect and only caused a lot of unnecessary work. This is extremly concerning as all of these devices are running on a network, that extensively uses ethernet has the 1 gig fiber speeds, and state of the art Wi-Fi 6E routers. In addition the fact that the Homepod is marketed as a home hub and as a matter hub but clearly fails in achieving these things as could be expected from Apple and the previous great experiences had with the Apple TV. To further add, the IKEA Trådfri and Dirigera hub is supposed to specifically, is fully approved and supported to work with Homekit and matter (even though that doesn't matter that much in this case) and is a mass market home smart system. It's also clear that this is an issue that isn't isolated to my case but has been extensively discussed by other IKEA and Homekit users and has according to others been reported to both Apple and IKEA multiple times but they seem to have taken no action. After reading these posts, it seems like Apple isn't willing to let users choose a prefered home hub or disable the homepods functionality as a home hub. I really don't care how Apple might eventually fix this issue, but just do it as soon as possible as this really breaks the functionality of my smart home.
Replies
1
Boosts
1
Views
2.6k
Activity
Apr ’23
Is there a way to support matter from iOS11.0?
Is there a way to support matter from iOS11.0? In the CHIP Tool iOS Sample Commissioner App readme doc says: Requires building and running the app to a physical device on iOS >= 15.4. Does it mean that the sample app matter framework cannot support iOS < 15.4? I have just changed the sample project configuration mini deployment version to iOS 11.0, built and ran, soon the app crashed Found MatterSupport.h is still empty, use Matter.h instead? Starting with 16.1 you need to use MatterSupport. In Xcode 14.2 iOS16.2 Framework MatterSupport.h is empty, should I use Matter.h instead? iShot_2023-03-15_19 37 28
Replies
1
Boosts
0
Views
1.1k
Activity
Mar ’23
HomeKit Matter Device Battery Level
Hello there, After including the power source cluster with it's feature maps, the HomeKit is not showing the remaining battery level for the Matter devices, I'm able to read back the power source cluster with my chip-tool for linux. My Apple System Specifications are, Apple BR -> Homepod Mini running tvOS 16.3.2 Matter Controller -> iPhone13 running iOS 16.3.1 Thanks in Advance.
Replies
0
Boosts
0
Views
1.7k
Activity
Mar ’23
MatterSupport framework MatterAddDeviceRequest Fails
[MatterAddDeviceRequest] Local browse failed; unable to start an add device operation (error: -65555: NoAuth) Failed to set up a device with error: -65555: NoAuth Code I am using -        let request = MatterAddDeviceRequest(         topology: .init(ecosystemName: "Test Echo", homes: [           .init(displayName: "Test Home 1"),         ]), setupPayload: nil, showing: .allDevices       )       do {         try await request.perform()         print("Successfully set up a device!")       } catch {         print("Failed to set up a device with error: (error)")       }
Replies
1
Boosts
0
Views
858
Activity
Mar ’23
Matter documentation help
I'm interested to learn more about this documentation: https://developer.apple.com/apple-home/matter/ It contains a bunch of information and also some statements I'm curious about. e.g. this one: Matter accessories can be managed in the Settings app Is the document referring to the iOS Settings app? I cannot find Matter accessories in the Settings App. I'd also like to learn more about the APIs (which and how to use) this document is telling about. Is anybody able to help?
Replies
0
Boosts
1
Views
1k
Activity
Mar ’23
iOS 16.1 API for Matter ecosystem implementation
Hello everyone, We are trying to manage matter devices within an iOS application. What we want is managing a matter fabric shared with other applications (iOS, Android, linux, ...). I read both 'Matter' and 'MatterSupport' documentations but neither framework seems to fit our needs. In the 'MatterSupport' documentations there is mention of an application Matter ecosystem implementation. I first thought it referenced a fabric but the API only allows us to specify an ecosytemName (Whatever that means). So my question is: How can we add devices to our own fabric with an official API ? And if not, does anyone know if the feature will be available in the near future ? Thank you in advance.
Replies
3
Boosts
0
Views
1.9k
Activity
Mar ’23
[Matter] Add device failure to iOS system fabric
Hi, When I use MatterAddDeviceRequest api in MatterSupport, system pop-up shows Pairing failed error. Could you please look into this why it occurs? If you provide the solution, it would be great help for me to add Matter device. Thank you. This is console log. 2022-12-26 15:53:53.151 [matter:1320010] 🔵 [1672037633151] [2422:1320010] CHIP: [DIS] Browsing for: _matterc._udp,_L1880 2 2022-12-26 15:53:53.153 [matter:1320316] 🟢 [1672037633152] [2422:1320316] CHIP: [DIS] Mdns: OnBrowseAdd name: 76549AC95D2520BF, type: _matterc._udp., domain: local., interface: 13 3 2022-12-26 15:53:53.153 [matter:1320316] 🟢 [1672037633152] [2422:1320316] CHIP: [DIS] Resolve type=_matterc._udp name=76549AC95D2520BF interface=13 4 2022-12-26 15:53:53.154 [matter:1320271] 🟢 [1672037633153] [2422:1320271] CHIP: [DIS] Mdns : OnNewInterface hostname:E2A2EB59C4923697.local. fullname:76549AC95D2520BF._matterc._udp.local. interface: 13 port: 42005 TXT:" VP=65521+32774 SII=6000 SAI=500 T=0 D=1880 CM=2 PH=36 PI=" 5 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Mdns: OnNewAddress interface: 13 ip:fd49:f8b0:496b:1:a6de:22c7:52c7:f7 6 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Mdns: OnNewAddress interface: 0 ip:218.38.137.27 7 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Mdns: Resolve success on interface 0 8 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Discovered node: 9 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] IP Address #1: 218.38.137.27 10 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Mrp Interval idle: not present 11 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Mrp Interval active: not present 12 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] TCP Supported: 0 13 2022-12-26 15:53:53.156 [matter:1320271] 🟢 [1672037633156] [2422:1320271] CHIP: [DIS] Commissioning Mode: 0 14 2022-12-26 15:54:23.155 [matter:1320271] E 🔴 [1672037663154] [2422:1320271] CHIP: [CTL] Discovery timed out
Replies
0
Boosts
1
Views
1.2k
Activity
Feb ’23
HMErrorDomain code=76 always occurs when using MatterSupport api
Hi, I wanted to use MatterAddDeviceRequest api in MatterSupport. When I called api, system pop-up shows up and then right after tapping 'Add to @' button, pop-up always shows HMErrorDomain 76 error. I found this code in HomeKit.HMError case keychainSyncNotEnabled = 76 I wonder that enabling keychain sync is mandatory to use MatterAddDeviceRequest api? Or could you tell me why this error always occurs? Thanks!
Replies
2
Boosts
1
Views
2k
Activity
Jan ’23