Hello fellow developers, I am in the process of developing an iOS application that support the Matter Framework. My goal is to enable user to commission their Matter-enabled device to a fabric and control them through the fabric. However, I stumbled upon a few questions and areas that I would greatly appreciate guidance on: Commission Process What is the recommended steps to successfully commission a Matter-enabled device? Using the Matter API I have reviewed the provided sample app in the CHIP repo. However, I find it a bit complex to understand fully (background context: I am a junior developer and have never work on iOS development before). I replicated the app using Swift since the sample is written in ObjC but often times got stuck on [connection] nw_read_request_report [C1] Receive failed with error "Operation timed out" log. How to effectively use the Matter API to handle commissioning, device control and other interactions with Matter-enabled devices? Keypair generation I have noticed that the framework doesn't provide an API with the keypair generation (correct me if I am wrong). What is the best practice or resources for handling the keypair generation within the Matter context? Matter Support vs Matter framework I need clarification on the roles of these two framework. From my understanding, MatterSupport adds Matter devices into my ecosystem(?) while Matter framework handles the commission and control in the Matter fabric. And we can use the Matter framework within the MatterSupport using the request handler to commission Matter-enabled device.

Hi Apple, I have a A vc, in this vc, I call this function to manager user home.manageUsers(completionHandler: { _ in }) But the result, the modalPresentationStyle of HMUserListViewController is overfullscreen. The HMUserListViewController is presented by system. The final UI effect is very strange, because the upper part of vc overlaps with the previous page. How can I fix this problem? Looking forward to your reply. Test device: iPhone 13 Pro iOS15.7

I had an issue a few days ago with a Schlage Encode Plus lock. Apparently, it had tried to update the firmware and encountered an issue. It dropped off the network with "not responding." I factory reset the lock and reset it back up, but when I try to add it to HomeKit, nothing works. It seems the "add accessory" piece of HomeKit is "stuck." The camera will no longer scan the QR code and when I try to add the device manually, I just get a spinning circle and I'm never given the opportunity to add it. I do see some data in console.log regarding HomeKit: cannot add handler to 3 from 3 - dropping There is another error message but it just says so I'm not sure what that could be. This has been reported in Feedback Manager. Any tips on how to clear this apparent logjam?

Hello, I'm trying to add matter devices to home kit. It end up saying as "Unable to add accessory" Using: Home Pod Mini Version:16.6 Model: MJ2E3 IOS version: 16.6

Hello, I trying to commission and joint thread matter device through I-phone ( ios 16.3.1) and apple home pod mini (16.3.2). After scanning QR code and following setup process it fails to add accessory and iPhone shows" Pairing with device failed" (attaching screen shot). I confirmed with device manufacturer, and it seems to be problem from apple side. Any help will be appreciated, Thank you.

Hello everyone, I purchased a level lock touch earlier this year. It’s a lock I have on my front door and side door. One of the ways it can be unlocked is with an NFC card. You can tap the card and the lock opens. Since the apple devices have NFC, and so does the level lock touch, I figured there must be a way to just unlock the door by tapping my devices. I asked apple about this and they said they couldn’t help me. I reached out to Level and they said apple will be selling a new level lock + which on October 21st which does exactly what I’m wanting to do….for $329! my question is, if both devices have NFC- couldn’t there just be some type of software update to allow this feature to happen. Instead- someone has to purchase a whole new lock!? I know it’s all about money but it just doesn’t make sense to me. does anyone maybe know of a third party app that can read the level lock nfc card and allow me to open the lock by tapping my device? In the mean time I’ll keep looking for another way besides shelling out another 329 for a lock. Smh

Does anyone know if this is even supported at the moment? I've tried pairing a sample light application based on Silicon Lab's EFR32 but it's unable to find the OTBR on the network. [module](GitHub - SiliconLabs/matter: Matter is creating more connections between more objects, simplifying development for manufacturers and increasing compatibility for consumers, guided by the Connectivity Standards Alliance.) I'm also using the RaspberryPi 4/RCP combination as directed by Silicon Lab's documentation. I have no problems pairing the devices to the OTBR directly through its chiptool interface but Home isn't discovering the Thread network or showing me options to add the OTBR devices. I'm currently running iOS 16.1 beta on my iPhone and I'm using a HomePod Mini which is on version 16.0 and has the HomeKit Matter Support profile installed.

Many customers of horizontal awnings complain that the logic is reversed. When the awning is extended it shows as closed and vice versa. When people talk or describe the state of the awning we say 'open' to extend and 'close' to retract. There are examples of people using it in scenes, or using Siri to ask to close all shutters and awnings, only to find the awnings fully extended the next morning after heavy rain. The overall status will also show the awnings 'Open' while they are not in use. This is all very annoying and confusing. There doesn't seem to be a difference in language between English and French, Dutch, German, ... when describing the operation of an awning. One can quickly find videos and instructions on operating awnings when 'open' refers to extending the horizontal coverage and 'closing' refers to retracting the horizontal coverage. Somfy (a manufacturer of motors for awnings and the Tahoma Switch = HomeKit Bridge) on their part claim that they cannot resolve this issue as they need to follow the HAP specification in order to pass HomeKit certification. This characteristic describes the current position of accessories. This characteristic can be used with doors, windows, awnings or window coverings. For windows and doors, a value of 0 indicates that a window (or door) is fully closed while a value of 100 indicates a fully open position. For blinds/shades/awnings, a value of 0 indicates a position that permits the least light and a value of 100 indicates a position that allows most light. -HAP specification 9.27 Current Position This is where Somfy points to with the claim they are obliged to use value '100' when it's fully retracted (closed, reported as open in HomeKit) and '0' when it's fully extended (open, reported as closed in HomeKit). Is this indeed a problem in the spec (i.e. should an awning's current position be determined like windows/doors?) or would Apple allow a manufacturer to interpret the spec according to what the user is expecting without loosing certification?

Hi,I have multiple Hue bridges set up in Homekit. Nearly 200 devices in all.When I get over about 170 devices Homekit stops syncing between my iPad and iPhone.I can see no documentation around what the maximum number of devices allowed in Homekit is, is anyone able to point me in the right direction?Many thanks!