Hello all, I have purchased 4 Homepod minis which update fine to public releases, I am currently on 17.4. I was testing with Apple and a patch is in the works so I wanted to test the beta software to see if it fixed my broken functionality within my homepods. The error message is "Loading failed, couldn't communicate with the helper application. The process was probably suspended before it could launch properly" from within the home application on my iPhone. I can update my other Apple devices to beta software either dev releases or public betas no problem. however, with the homepods, it just is not working. I have removed 1 of the 4 homepods hard reset it and set it up again etc to no avail. I phoned Apple support there solution was to try a different network or give it a shot on here. I will try a different network however I do not have another Apple device which can establish a new accessory to my home i.e. another iPhone or an iPad. Are there any known workarounds? I have searched previously for a solution but all I got were results relating to Xcode and people-building applications. not related specifically to the home pod or homepodOS Sorry if this has been posted in the wrong section of these forums. Thank you all for the help. Antonio.

I have AirPort Extreme connected via eth switch to my MacBook And I have certified homekit device that broadcasting Apple IE as specified in the WAC Requirement document. the Airport utility is not able to see my WAC device. What I am missing? In the WAC2 document, in the test scenario, the Airpot utility should see the homekit devices (WAC) BTW: I can see the WAC devices with my iPhone as "SET UP New Device..."

I have a smart camera device that can be added as an accessory to a homeKit. I want to implement a subset of functionalities of the smart camera behind a paid subscription or a paywall. Anyone aware if this has been done before? i.e. conditionally exposing services on a Homekit accessory as a paid feature? So far neither have I seen any such examples and also nowhere in the apple docs does it say that you can't. So looking for any information regarding this. The questions are Does apple support paid services in Homekit accessories? If not, does it prevent people from implementing customized solutions?

Is there a good source of documentation on what IP ports and protocols are used by HomeKit accessories?

Hello everyone, I'm trying to configure my WAC device trough an App. This App finds the device without problems using startSearchingForUnconfiguredAccessoriesMatchingPredicate but when I try to use configureAccessory method I get only 3 messages in Xcode and nothing happens. These messages are: 2024-03-14 12:55:56.261969+0000 App[1394:380785] ### WAC: -[EAWiFiUnconfiguredAccessoryBrowserManager configureAccessory:withConfigurationUIOnViewController:]_block_invoke_3:368 Other Region SKU 2024-03-14 12:55:56.266191+0000 App[1394:374248] ### WAC: _notificationCleanup:42 responseFlags: 3 ### WAC: _notificationCleanup:43 responseFlags: 3 For me they don't look like an Error but would be nice if someone could give me some advice on this, I didn't find nothing about it. Thanks in advance!

Hi all, We are developing a Smart Home / IoT product that integrates into HomeKit. The integration is mostly done and interation with the product works great. We have only one problem: naming inside the home app. Each time we add one of our devices to the home app, the services names are changed to the name of the accessory. Here is an example with the homekit tree: Accessory Service: Accessory Information Characteristrics: name = "my accessory" Service: Light Bulb Characteristics: name = "light 1" Service: Light Bulb Characteristics: name = "light 2" Service: Light Bulb Characteristics: name = "light 3" Service: Light Bulb Characteristics: name = "light 4" Service: Temperature Sensor Characteristics: name = "temperature sensor 1" When adding this device with 4 lights and 1 temperature sensor to homekit, all the services inside the app gets renamed "my accessory". They do not keep their name. It is especially strange since HomeKit knows about the names of the services since if I modify the name of the first light, HomeKit will suggest (in the background on the text input in gray) to rename it "light 1". I know that my characteristics declaration are correct because I verified it with the HomeKit Accessory Tester. What I can do so that the services offered by my device are not renamed to the name of the accessory itself ? Thanks in advance.

My matter accessory define an endpoint of type light, with a custom cluster. if I connect my accessory using Home app, I'm I supposed to find HMService/HMCharacteristic corresponding to my custom matter cluster? Is there any requirement on the custom cluster to have it visible in HomeKit ? Thanks.

Greetings! I've added a Matter accessory via the Apple Home app. In my app, I'm attempting to commission this device and add it to my fabric. However, when I try to open the commissioning window, I receive an error stating, MTRBaseDevice doesn't support openCommissioningWindowWithDiscriminator over XPC. It appears that opening a commissioning window via an XPC connection is not yet supported. Is there another method to commission the device? Can I retrieve the setup payload from the MTRBaseDevice object or the shared MTRDeviceController? Here's the simplified version of my code: var home: HMHome // HMHome received via HMHomeManager var accessory: HMAccessory = home.accessory[0] // my Matter-supported accessory let deviceController = MTRDeviceController.sharedController( withID: home.matterControllerID as NSCopying, xpcConnect: home.matterControllerXPCConnectBlock ) let device = MTRBaseDevice( nodeID: accessory.matterNodeID as NSNumber, controller: deviceController ) device.openCommissioningWindow( withDiscriminator: 0, duration: 900, queue: .main) { payload, error in if let payload { // payload not received } else if let error { // I'm getting here "Error Domain=MTRErrorDomain Code=6 "(null)"" // and "MTRBaseDevice doesn't support openCommissioningWindowWithDiscriminator over XPC" logged in the console print(error) }

Dear All, we have an old app that supports HomeKit. As company we exited the MFi program. Now we need to update the app to do some minor changes (XCode update, recompilation and Font changes). No firmware changes. Does it need to go through the certification process? Thanks

Home App is not picking up current state, for example if I open the door I push button() to open and set current->setVal(2), the app shows it as opening, but if my door has obstruction the gate controller will stop and reverse automatically and the current->setVal(1) will be triggered as the gate closes by the sensor. Mean wile home app will say its still opening even though the current state has been set and notified as closed.

It seems that HMHomeManager..accessories array lists everything... except HomePods and AppleTVs. Is there way to discover all HomePods? And once discovered, is there way to play sounds clips in some or all rooms in the house?

I have a custom device that connects to my swift app over BLE. The device can send commands, which need to be forwarded to HomeKit. This works when the app is open, but when it is in the background, I get: "Error turning off light: Missing entitlement for API." Is there a way to forward these controls from my app to HomeKit from the appplications background?

I have been using the HomePod 17.3 Beta for while and wanted to reset it yesterday. Now I can not set up both my HomePods (one OG and one Mini) anymore. Setup with iPhone and iPad keeps failing after 2 minutes. When the Mini is plugged into the Mac and I click "restore" I get an error message "Update server could not be contacted". Any idea?

The Aqara D100 smart lock has an integrated doorbell. I can't see a way to integrate this into Homekit so I can have the doorbell sound on Homepod minis throughout the house.

Hi, Recently I bought 2 HomePod minis and placed them in my kitchen and bathroom. I have noticed that they keep their alarms/reminders device-local and take priority over any other device. For example I can hold up my phone, say something like "hey siri set alarm for 7am" and the kitchen echo will respond something like "none of your devices can do that" (obviously sound quality suffered from distance) or worse, it sets an alarm on the device not my phone, waking everyone in the household not just me. Another annoying habit it has is to set a reminder on one device, then later I say something like "cancel my reminders", accidentally the other HomePod picks it up, says something like "I cancelled all your reminders" then a few minutes later the first HomePod will still remind me - so it's not even shared across HomePods. Setting wake-up alarms gotten so bad and complicated (walk out of a room, whisper to the phone directly) I had to disable both HomePods from listening to "siri". Now all they are is expensive decoration (except when once a week we listen to some music on it). Is there no way to make HomePods not to be the highest priority devices and use alarms/reminders from the phone (like it does with shopping lists)? This annoying experience I would expect from MS and Alexa maybe, but not Apple.

I tried to add my Eve Weather and Door & Window. It failed continuously and immediately with below log. Nov 23 16:24:50 iPhone-2 homed(HomeKitMatter)[173] <Error>: [589021415/1061261160] CHIP Stack is not running Nov 23 16:24:50 iPhone-2 homed(HomeKitMatter)[173] <Error>: [589021415/1061261160] CHIP Accessory pairing failed with error Error Domain=HAPErrorDomain Code=3 Nov 23 16:24:50 iPhone-2 homed(HomeKitDaemon)[173] <Error>: [188914BD-5163-425C-9E59-CAE9BFA1A288] Failed to stage CHIP accessory pairing for request UUID <private>: Error Domain=HMErrorDomain Code=18 "Pairing Failed" UserInfo={NSLocalizedDescription=Pairing Failed, NSUnderlyingError=0xc508b7df0 {Error Domain=HAPErrorDomain Code=3}} Nov 23 16:24:50 iPhone-2 homed(HomeKitDaemon)[173] <Notice>: Answering incoming message HMASC.m.stageCHIPAccessoryPairingInSteps (2D3E9A84-52E8-4614-8B79-A23A5DBC245D) from client 'HomeUIService' that does expect a response with error Error Domain=HMErrorDomain Code=18 "Pairing Failed" UserInfo={NSLocalizedDescription=Pairing Failed, NSUnderlyingError=0xc508b7df0 {Error Domain=HAPErrorDomain Code=3 "(null)"}} Nov 23 16:24:50 iPhone-2 homed(HomeKitMetrics)[173] <Error>: [188914BD-5163-425C-9E59-CAE9BFA1A288] tag="stagedPairingFailure" desc="Failed to stage CHIP accessory for request UUID" errorDomain="HMErrorDomain" errorCode="18" underlyingErrorDomain="HAPErrorDomain" underlyingErrorCode="3" Nov 23 16:24:50 iPhone-2 HomeUIService(HomeKit)[521] <Error>: [CF47D609-EF2F-44E3-96EC-89906F4F33C4] Failed to stage CHIP accessory pairing in steps: Error Domain=HMErrorDomain Code=18 UserInfo={NSLocalizedDescription=<private>, NSUnderlyingError=0x283431fe0 {Error Domain=HAPErrorDomain Code=3}}

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?

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.