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

Posts under Matter tag

130 Posts

Post

Replies

Boosts

Views

Activity

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.4k
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
598
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.3k
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.3k
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.5k
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
824
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.8k
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
1.8k
Jan ’23
HomeKit support for Matter
Why do devices that Matter over WiFi still need homepod mini for control? Can't the home app communicate directly with the device. How to get devices that Matter over Thread to join the HomePod Mini's Thread network. Do you need any additional conditions? As for the Matter Bridge, is the Home app still unsupported now? Can the future plan be announced?
1
0
1.9k
Jan ’23
Commissioning failure to iOS system fabric
Hi, When I use MatterAddDeviceRequest api in MatterSupport, system pop-up shows error after CASE session. After getting Commissioning complete status, it gets unexpected error as follow. error 20:03:52.483305+0900 homed [CHIPAccessoryServer[2929489573/1]] 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.} 2error 20:03:52.483479+0900 homed [CHIPAccessoryServer[2929489573/1]] 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." 3UserInfo={NSLocalizedDescription=The specified attribute or attribute data field or entry does not exist on the device.} Serial number is optional for Matter spec. Could you please tell me why this error occurs? Here is the console log, default 20:03:52.311598+0900 homed DevicePairingDelegate Commissioning complete. NodeId 2929489573 Status ../../../../../../../../Sources/CHIPFramework/connectedhomeip/src/controller/CHIPDeviceController.cpp:1962: Success //// 2default 20:03:52.311708+0900 homed 🟢 [1669201432311] [145:1833690] CHIP: [DMG] ICR moving to [AwaitingDe] default 20:03:52.313643+0900 homed 🟢 [1669201432313] [145:1833690] CHIP: [CTL] OperationalSessionSetup[1:00000000AE9C76A5]: State change 1 --> 5 20default 20:03:52.313684+0900 homed 🟢 [1669201432313] [145:1833690] CHIP: [DMG] SendReadRequest ReadClient[0x9008c1a80]: Sending Read Request 21default 20:03:52.313947+0900 homed 🔵 [1669201432313] [145:1833690] CHIP: [IN] Prepared secure message 0x9008b6ab8 to 0x00000000AE9C76A5 (1) of type 0x2 and protocolId (0, 1) on exchange 52688i with MessageCounter:24415435. 22default 20:03:52.313988+0900 homed 🔵 [1669201432313] [145:1833690] CHIP: [IN] Sending encrypted msg 0x9008b6ab8 with MessageCounter:24415435 to 0x00000000AE9C76A5 (1) at monotonic time: 000000002E0C7575 msec 23default 20:03:52.314301+0900 homed 🟢 [1669201432314] [145:1833690] CHIP: [DMG] MoveToState ReadClient[0x9008c1a80]: Moving to [AwaitingIn] 24default 20:03:52.401751+0900 homed 🔵 [1669201432384] [145:1833686] CHIP: [DIS] Checking node lookup status after 202 ms 25default 20:03:52.401818+0900 homed 🟢 [1669201432384] [145:1833686] CHIP: [DIS] OperationalSessionSetup[1:00000000AE9C76A5]: Updating device address to UDP:[fe80::464f:8eff:fe02:f596%en0]:5540 while in state 2 26default 20:03:52.401899+0900 homed 🟢 [1669201432384] [145:1833686] CHIP: [CTL] OperationalSessionSetup[1:00000000AE9C76A5]: State change 2 --> 3 27default 20:03:52.480226+0900 homed 🔵 [1669201432480] [145:1833686] CHIP: [EM] Received message of type 0x10 with protocolId (0, 0) and MessageCounter:71854311 on exchange 52687i 28 29error 20:03:52.480473+0900 homed 🔴 [1669201432480] [145:1833686] CHIP: [EM] OnMessageReceived failed, err = ../../../../../../../../Sources/CHIPFramework/connectedhomeip/src/messaging/ExchangeMgr.cpp:275: CHIP Error 0x00000070: Unsolicited msg with originator bit clear 30 31default 20:03:52.480604+0900 homed 🔵 [1669201432480] [145:1833686] CHIP: [EM] Received message of type 0x5 with protocolId (0, 1) and MessageCounter:71854312 on exchange 52688i 32default 20:03:52.480709+0900 homed 🟢 [1669201432480] [145:1833686] CHIP: [EM] Found matching exchange: 52688i, Delegate: 0x9008c1a90 33default 20:03:52.482672+0900 homed 🟢 [1669201432480] [145:1833686] CHIP: [EM] Rxd Ack; Removing MessageCounter:24415435 from Retrans Table on exchange 52688i 34default 20:03:52.482789+0900 homed 🟢 [1669201432480] [145:1833686] CHIP: [EM] Removed CHIP MessageCounter:24415435 from RetransTable on exchange 52688i 35default 20:03:52.482897+0900 homed 🟢 [1669201432481] [145:1833686] CHIP: [EM] Sending Standalone Ack for MessageCounter:71854312 on exchange 52688i 36default 20:03:52.482974+0900 homed 🔵 [1669201432481] [145:1833686] CHIP: [IN] Prepared secure message 0x16d319228 to 0x00000000AE9C76A5 (1) of type 0x10 and protocolId (0, 0) on exchange 52688i with MessageCounter:24415436. 37default 20:03:52.483037+0900 homed 🔵 [1669201432481] [145:1833686] CHIP: [IN] Sending encrypted msg 0x16d319228 with MessageCounter:24415436 to 0x00000000AE9C76A5 (1) at monotonic time: 000000002E0C761D msec 38default 20:03:52.483129+0900 homed 🟢 [1669201432481] [145:1833686] CHIP: [EM] Flushed pending ack for MessageCounter:71854312 on exchange 52688i 39default 20:03:52.483239+0900 homed 🟢 [1669201432482] [145:1833686] CHIP: [CTL] Response Time: PFvPvN4chip4SpanIKcEEE+1193323840 0.168765 seconds 40 41error 20:03:52.483305+0900 homed [CHIPAccessoryServer[2929489573/1]] 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.} 42error 20:03:52.483479+0900 homed [CHIPAccessoryServer[2929489573/1]] 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." 43UserInfo={NSLocalizedDescription=The specified attribute or attribute data field or entry does not exist on the device.} error 20:03:53.035959+0900 homed [CHIPPluginDescriptorClusterManager] Mandatory characteristic <private> cannot be found in clusters in use at endpoint 1. error 20:03:54.150008+0900 HomeUIService [45A57529-5E82-4090-94F2-80EE3A383CA7] Failed to stage CHIP accessory pairing in steps: Error Domain=HMErrorDomain Code=2 error 20:03:54.150338+0900 HomeUIService -[HSSetupStateMachineCHIPPartnerConfiguration stageCHIPAccessory]_block_invoke Failed to stage CHIP accessory: Error Domain=HMErrorDomain Code=2 default 20:03:54.150574+0900 HomeUIService stageCHIPAccessory hit error Error Domain=HMErrorDomain Code=2 Thank you.
1
0
1.3k
Dec ’22
'Display As' not showing in accessory setting
Since the latest home update, the subject item is no longer showing for certain devices which are now defaulting to Light (rather then Fan or Outlet) What controls this option? can it be forced on in some way when adding / modifying the device through a custom app? Many thanks
Replies
0
Boosts
0
Views
665
Activity
May ’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.4k
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
598
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.3k
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.3k
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.5k
Activity
Mar ’23
Code=62 "Unable to connect to accessory. Check the setup code and try again."
Hi, I have Eve devices and I wanted to add them but popup shows that "Could Not Add Accessory" "Unable to connect to accessory. Check the setup code and try again." I scanned QR code which was made from https://qr.evehome.com/ Serial Number: SV17L1A00918 Could you please help this problem? Thank you.
Replies
0
Boosts
1
Views
875
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
824
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.8k
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
1.8k
Activity
Jan ’23
HomeKit support for Matter
Why do devices that Matter over WiFi still need homepod mini for control? Can't the home app communicate directly with the device. How to get devices that Matter over Thread to join the HomePod Mini's Thread network. Do you need any additional conditions? As for the Matter Bridge, is the Home app still unsupported now? Can the future plan be announced?
Replies
1
Boosts
0
Views
1.9k
Activity
Jan ’23
Matter.framework API
I don't find any API documentation of the Matter.framework. Is it going to be private or can we use it to create custom controllers, which are independent of HomeKit?
Replies
1
Boosts
0
Views
1.4k
Activity
Dec ’22
Commissioning failure to iOS system fabric
Hi, When I use MatterAddDeviceRequest api in MatterSupport, system pop-up shows error after CASE session. After getting Commissioning complete status, it gets unexpected error as follow. error 20:03:52.483305+0900 homed [CHIPAccessoryServer[2929489573/1]] 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.} 2error 20:03:52.483479+0900 homed [CHIPAccessoryServer[2929489573/1]] 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." 3UserInfo={NSLocalizedDescription=The specified attribute or attribute data field or entry does not exist on the device.} Serial number is optional for Matter spec. Could you please tell me why this error occurs? Here is the console log, default 20:03:52.311598+0900 homed DevicePairingDelegate Commissioning complete. NodeId 2929489573 Status ../../../../../../../../Sources/CHIPFramework/connectedhomeip/src/controller/CHIPDeviceController.cpp:1962: Success //// 2default 20:03:52.311708+0900 homed 🟢 [1669201432311] [145:1833690] CHIP: [DMG] ICR moving to [AwaitingDe] default 20:03:52.313643+0900 homed 🟢 [1669201432313] [145:1833690] CHIP: [CTL] OperationalSessionSetup[1:00000000AE9C76A5]: State change 1 --> 5 20default 20:03:52.313684+0900 homed 🟢 [1669201432313] [145:1833690] CHIP: [DMG] SendReadRequest ReadClient[0x9008c1a80]: Sending Read Request 21default 20:03:52.313947+0900 homed 🔵 [1669201432313] [145:1833690] CHIP: [IN] Prepared secure message 0x9008b6ab8 to 0x00000000AE9C76A5 (1) of type 0x2 and protocolId (0, 1) on exchange 52688i with MessageCounter:24415435. 22default 20:03:52.313988+0900 homed 🔵 [1669201432313] [145:1833690] CHIP: [IN] Sending encrypted msg 0x9008b6ab8 with MessageCounter:24415435 to 0x00000000AE9C76A5 (1) at monotonic time: 000000002E0C7575 msec 23default 20:03:52.314301+0900 homed 🟢 [1669201432314] [145:1833690] CHIP: [DMG] MoveToState ReadClient[0x9008c1a80]: Moving to [AwaitingIn] 24default 20:03:52.401751+0900 homed 🔵 [1669201432384] [145:1833686] CHIP: [DIS] Checking node lookup status after 202 ms 25default 20:03:52.401818+0900 homed 🟢 [1669201432384] [145:1833686] CHIP: [DIS] OperationalSessionSetup[1:00000000AE9C76A5]: Updating device address to UDP:[fe80::464f:8eff:fe02:f596%en0]:5540 while in state 2 26default 20:03:52.401899+0900 homed 🟢 [1669201432384] [145:1833686] CHIP: [CTL] OperationalSessionSetup[1:00000000AE9C76A5]: State change 2 --> 3 27default 20:03:52.480226+0900 homed 🔵 [1669201432480] [145:1833686] CHIP: [EM] Received message of type 0x10 with protocolId (0, 0) and MessageCounter:71854311 on exchange 52687i 28 29error 20:03:52.480473+0900 homed 🔴 [1669201432480] [145:1833686] CHIP: [EM] OnMessageReceived failed, err = ../../../../../../../../Sources/CHIPFramework/connectedhomeip/src/messaging/ExchangeMgr.cpp:275: CHIP Error 0x00000070: Unsolicited msg with originator bit clear 30 31default 20:03:52.480604+0900 homed 🔵 [1669201432480] [145:1833686] CHIP: [EM] Received message of type 0x5 with protocolId (0, 1) and MessageCounter:71854312 on exchange 52688i 32default 20:03:52.480709+0900 homed 🟢 [1669201432480] [145:1833686] CHIP: [EM] Found matching exchange: 52688i, Delegate: 0x9008c1a90 33default 20:03:52.482672+0900 homed 🟢 [1669201432480] [145:1833686] CHIP: [EM] Rxd Ack; Removing MessageCounter:24415435 from Retrans Table on exchange 52688i 34default 20:03:52.482789+0900 homed 🟢 [1669201432480] [145:1833686] CHIP: [EM] Removed CHIP MessageCounter:24415435 from RetransTable on exchange 52688i 35default 20:03:52.482897+0900 homed 🟢 [1669201432481] [145:1833686] CHIP: [EM] Sending Standalone Ack for MessageCounter:71854312 on exchange 52688i 36default 20:03:52.482974+0900 homed 🔵 [1669201432481] [145:1833686] CHIP: [IN] Prepared secure message 0x16d319228 to 0x00000000AE9C76A5 (1) of type 0x10 and protocolId (0, 0) on exchange 52688i with MessageCounter:24415436. 37default 20:03:52.483037+0900 homed 🔵 [1669201432481] [145:1833686] CHIP: [IN] Sending encrypted msg 0x16d319228 with MessageCounter:24415436 to 0x00000000AE9C76A5 (1) at monotonic time: 000000002E0C761D msec 38default 20:03:52.483129+0900 homed 🟢 [1669201432481] [145:1833686] CHIP: [EM] Flushed pending ack for MessageCounter:71854312 on exchange 52688i 39default 20:03:52.483239+0900 homed 🟢 [1669201432482] [145:1833686] CHIP: [CTL] Response Time: PFvPvN4chip4SpanIKcEEE+1193323840 0.168765 seconds 40 41error 20:03:52.483305+0900 homed [CHIPAccessoryServer[2929489573/1]] 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.} 42error 20:03:52.483479+0900 homed [CHIPAccessoryServer[2929489573/1]] 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." 43UserInfo={NSLocalizedDescription=The specified attribute or attribute data field or entry does not exist on the device.} error 20:03:53.035959+0900 homed [CHIPPluginDescriptorClusterManager] Mandatory characteristic <private> cannot be found in clusters in use at endpoint 1. error 20:03:54.150008+0900 HomeUIService [45A57529-5E82-4090-94F2-80EE3A383CA7] Failed to stage CHIP accessory pairing in steps: Error Domain=HMErrorDomain Code=2 error 20:03:54.150338+0900 HomeUIService -[HSSetupStateMachineCHIPPartnerConfiguration stageCHIPAccessory]_block_invoke Failed to stage CHIP accessory: Error Domain=HMErrorDomain Code=2 default 20:03:54.150574+0900 HomeUIService stageCHIPAccessory hit error Error Domain=HMErrorDomain Code=2 Thank you.
Replies
1
Boosts
0
Views
1.3k
Activity
Dec ’22
Does ios16.1 support mode select cluster in matter
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
Replies
0
Boosts
0
Views
1.4k
Activity
Nov ’22
performMatterEcosystemAccessorySetup removed in iOS 16.1?
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?
Replies
0
Boosts
0
Views
1.1k
Activity
Sep ’22
Connecting to Matter device on iOS 16
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).
Replies
5
Boosts
1
Views
4.6k
Activity
Sep ’22
Matter in the Xcode 14 Release Candidate?
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?
Replies
2
Boosts
0
Views
1.6k
Activity
Sep ’22