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?

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

I recently updated my HomePod mini to version 16.3, which enables the temperature and humidity sensors. However, in the HomeKit iPad app I've developed, the HomePod mini does not show up in HMHome.accessories. I expected it show up there with a service of type HMServiceTypeTempatureSensor.

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.

Updated version of this post My HomePod mini is now on version 16.4, so the the temperature and humidity sensors are enabled. The data properly shows up in the Home app on my various devices. In my HomeKit iPad app running on Mac Catalyst, however, the data does not show up. I would expect the HomePod mini to show up in HMHome.accessories with a service of type HMServiceTypeTempatureSensor. I see all of my other HomeKit accessories, just not the HomePod mini. I have tried with the latest Xcode (14.3) and highest available iOS Target and Minimum Deployment (16.4), macOS version 13.3. I have not, as of this writing, upgraded my HomeKit architecture, however. Note that I haven't tried the app on an actual iPad (and the iOS simulator doesn't expose my HomeKit environment.)

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

I downloaded HomeKit ADK 6.3.zip and found that it is missing the Makefile.Sensors file. Is this normal or should I download it from somewhere else?

I am trying to read register values from an MFi Authentication Coprocessor 3.0 chip MFI343S0017 by I2C. But all the return values are 0x00 instead of the expected values.What can possibly be going wrong?

A new feature in Settings > privacy & Security> Location Services that allows users to disable location access for all installed 3rd party applications. I think this is a great idea. It would save battery life and improve privacy for users. It would also be helpful for tracking kids and teenagers, as well as for people with Alzheimer's or dementia and syndrome down people. Apple and Google should store children and teenagers' school locations on their Apple or Google accounts. I think this is a good idea, but I don't think it should be mandatory. Parents should have the option of whether or not to share their child's school location. this helps to protect our teenagers to be safe. Apple should distinguish between known locations, such as home, work, and school. This would be a helpful feature for apps that need to know where the user is located. For example, a delivery app or Amazon iOS App could use this information to let the user know when their package is expected to arrive. Apple should create a Location Known Kit for Location access. This would allow apps to share location information with each other. and there is no need to check over and over by different 3rd party who installed multiple and different applications to check the Locations over and over and it's a disaster that if users are at home or at workplace or at school most majority of the time. please note above new enhancement might help a lot of Apple home and Google Home's routine and automation feature to make them possible This would save battery life and improve performance. I think these are all great ideas. I hope that Apple will consider implementing them in future versions of iOS and iPadOs and Watch OS. Thanks in advance. Best Pooya Mohammadhossein Pooya M

Sorry if this is a stupid question but I haven't been able to find any information on whether an app can request and receive weatherKit data - the weather - while in the background. My app (AirCompare) makes extensive use of background URL sessions to fetch and process weather data. If certain conditions are met, a notification alert is sent to the user so the user can decide whether to activate the app. For instance if rain is in the forecast, the app alerts the user that they might want to close their windows. Making the app active will execute HomeKit control and accomplish that. Will I be able to replace the background URL session with the appropriate code and be able to fetch weather data in the background?

We developed a HomeKit bridge for our client to bridge their BLE-based dimmers to HomeKit. One end customer found that, on every 1 or 2 days, the bridged accessories that he already moved to different rooms and had automation set up were moved back to the Default Room, and related automation lost. It’s like the bridged accessories were removed and re-added to HomeKit. We traced the problem on the bridge side, but couldn’t find any hint. The bridge just received various requests from HomeKit clients (probably Apple TV, HomePod or iPhone), and the bridge replied correctly on the number of bridged accessories and their information. Anyone with HomeKit bridge (such as Philips Hue hub?) experience this too?

Hi community, my test iPhone running the IOS 17 beta crashed after removing an item from Homekit. It is now stuck in a boot loop - showing the home screen for a split second before then a turning wheel for about 5 seconds and again the home screen for a split second. Entering DFU mode and recovery mode is possible, but the device doesn't pop up on either of my two Macs (tested on macOS 16 and 17) - the device also doesn't pop up under 'system report's USB page or via Apple Configurator. Of course I tried three different cables as well. What can I do? Is this iPhone bricked? Have a Genius appointment for Tuesday - but if we can solve before together, even better.

When viewing this webpage, hobbyists, like me, are told to visit this website to download the non-commercial HAP specification. Unfortunately that website just redirects here, which does not say anything about the non-commercial specification.

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

I'm attempting to control a television (an recent LGTV) via HomeKit. When I scan all of the accessories (through HMHome.accessories, and also by querying each room separately) most of my devices show up -- but not my TVs or Apple TVs, and a couple of other things like an AVR. These devices show up on my Home app, assigned to specific rooms, and I can use that app and Shortcuts, to control the TV. Is there any way to find these devices through the HomeKit API? Or are there other APIs which I need to use for them, perhaps AirPlay?

Hello there, I recently updated both my iPhone and HomePod to the latest iOS 17 Public Beta and have been encountering an issue with Siri activation. In particular, I am unable to activate Siri just by saying "Siri". Specifically, I have adjusted the settings on my HomePod to allow activation via either "Siri" or "Hey Siri" (in my case, "Oye Siri", since I'm using Siri in Spanish). After saving these settings and rebooting all of my devices, I have found that Siri will not activate unless I use the full "Hey Siri" prompt ("Oye Siri"). I would expect that, following the update and the adjustment to these settings, I should be able to activate Siri just by saying just "Siri" but this does not appear to be the case. I would appreciate any assistance with rectifying this issue. To summarize: I've updated to iOS 17 Public Beta on all of my Apple devices. The "Activate via "Siri" or "Hey Siri"" option is set to "Yes". Even after saving and restarting, Siri only activates with "Hey Siri" ("Oye Siri"). If anyone has encountered similar issues or has any advice or potential solutions, I would greatly appreciate your input. Also, if you feel I should be reporting this as a possible bug in the beta software, please let me know. Thank you all for your time and help.

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

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?