Hey all, first post here (I think).
Upon updating to 26.1 Beta my HomeKit lights are acting weird in Apple Home. I can turn them all on and off - and on some I can even click the button for Adaptive Lighting successfully. But no color changes by touch in the Home app.
When I try to pick a color in Apple Home, I can slide the color “bubbles” back and forth, but when I click one, nothing happens. I can, however, change them just fine in the Aqara app, by voice with Siri, and with Scenes.
I gather this is probably just a normal Apple Beta hiccup, but just wanted to check here to see if anyone else has seen this too and/or maybe found a band-aid.
Before putting myself through the pain of resetting 18 lights, I tested a couple bulbs by deleting/re-installing them in both Apple and Aqara apps, but no dice.
On Reddit, I’ve seen a few posts of users with the same issue with Aqara, Hue, and Nanoleaf lights, so I know it’s not just me. Also some that report no issues with similar setups on the same beta. So I guess I just got ‘lucky’.
Not a huge deal yet because they work everywhere else except by touch in the Apple Home app. I imagine it’s just a waiting game for Apple to fix whatever they broke with the Beta but just thought I’d throw it here as well and see if I get a nibble.
@gregg37 Hey! It seems you’re facing an issue with color picking not working in the Apple Home app after updating to 26.1 Beta for your Aqara HomeKit lights. From the reference information we have, there isn’t a direct solution to this specific problem.
It’s possible, as you guessed, that this is a bug in the Apple Beta version. Since the lights can be controlled in other ways like in the Aqara app, by Siri voice commands, and with Scenes, it’s likely an issue specific to the Apple Home app’s color picker functionality.
I encourage our community members to chime in if they’ve encountered the same problem or found any workarounds. If you have any suggestions for improvement regarding this issue, you can submit manual customer service feedback. This way, we can all work together to drive improvements and figure out what might be causing this. Let’s hope we can find a solution or that Apple fixes this in a future update!
1 Like
Thanks! I figured it’s just a waiting game to get the update that fixes whatever they broke. But figured I’d drop it in here just in case.
I’ll report back if there’s any new info/fixes/whatever. 
@gregg37 That’s really kind of you! Your sharing is super valuable as it helps us be aware of such issues in the community. We really appreciate you taking the time to post this. Looking forward to your updates. If you have any other thoughts or run into new things, don’t hesitate to share them with us. And if you have suggestions for improvement, remember to submit manual customer service feedback.
1 Like