# \[APP\]\[Pro\] HomeKit Controller - for a better Homey

**URL:** <https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520>\
**Category:** Apps\
**Tags:** app, homey-pro\
**Created:** [November 13, 2023, 2:48pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520 "2023-11-13T14:48:49Z")\
**Posts on this page:** 19\
**Page:** 31

<div class="post-metadata">

**Author:** ![Rowel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rowel/32/47723_2.png) [@Rowel](https://community.homey.app/u/Rowel)\
**Post date:** [October 31, 2026, 7:37pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/624 "2026-10-31T19:37:46Z")

</div>

Ok, tried that with the original app but not with the test version. Thanks!

I feel kinda stupid for not having done so. Power cycled the FP2 and it connected! But then I got the same issue [Oren\_Malki](https://community.homey.app/u/oren_malki) had in December '23 and posted about in this thread “All Good, This device works fine but you cannot control it.”

So I’m off now to remove it from Homey, Aqara app, reset it and try all over again!

For completeness of the report. After adding it it starts as “Unavailable” with this error message: “Cannot read properties of undefined (reading ‘on’) cannot load Accessories”. Then once available it’s the “All Good” message… Just removed and readded in Homey just to see if I could try to avoid the reset but same result…

Update: Removed from Homey and Aqara app, reset the FP2. Re-added in Aqara, then Homey… but the problem persists.

Update 2: Installed the regular version of the HomeKit Controller app again. FP2 removed from Homey and Aqara and reset. Reconnected to Aqara and, after powercycle it did connect to Homey though I did get error code: “pairSetup M2: Error: 6 =\> Unavailable, retry”. But it showed up in Homey and it’s working!

---

<div class="post-metadata">

**Author:** ![Andrea\_Artoni](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andrea_artoni/32/181827_2.png) [@Andrea\_Artoni](https://community.homey.app/u/Andrea_Artoni)\
**Post date:** [November 2, 2026, 7:16pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/625 "2026-11-02T19:16:43Z")

</div>

@Martin_Verbeek

I’m having trouble pairing a Xiaomi Mi Bedside Lamp 2 (MJCTD02YL) with HomeKit Controller on Homey Self-Hosted Server. Same result on 2.2.9 and on the 3.3.7 test version.

What happens:

- Discovery works fine: single IPv4 address, TXT sf=1, ff=2, pairMethod 0, port 80.
- Every pair-setup attempt fails right after M1 with “HomekitControllerError: M2: Error: 1” (6-byte TLV reply, so kTLVError\_Unknown), thrown in PairingProtocol.parsePairSetupM2 (pairing-protocol.js:242) via HttpClient.startPairing (http-client.js:172). The PIN is never used, since the lamp rejects the M1 itself.
- Same result on the first attempt after an app restart, and on a lamp that I factory-reset (new HAP id, s#=1, c#=1).
- The lamp was previously paired fine with Home Assistant.

One thing I noticed in the log: “startPairing… 0 2” (method 0, flags 2), and 2 is exactly the lamp’s TXT ff value. If that value ends up in the M1 as a Flags TLV (0x13), a strict HAP stack like this lamp’s could be answering “Unknown”, while the Aqara FP2 (also ff=2) just ignores it. Could you check what the M1 body contains, and if needed send no Flags for a plain pair-setup? A clean M1 should be just Method=0 and State=1.

I can capture the POST /pair-setup with tcpdump if that helps, and I’m happy to test any build. I can attach the full app log (PIN redacted) if useful.

Thanks a lot for the app!

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [November 3, 2026, 3:33pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/626 "2026-11-03T15:33:52Z")

</div>

3.3.7 is now live. This is a pretty big change. The more notable changes are:

I have moved the customized labels for zones and other multiple similar capabilities to the device REPAIR place, that offers much more flexibility to customize some things.

When adding devices it will list more information on devices that are available or not available to pair, it also is designed such that you can leave it open, it will update regularly with newly discovered devices in the network.

BLE is added as beta

---

<div class="post-metadata">

**Author:** ![Aimen\_Mutair](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aimen_mutair/32/180678_2.png) [@Aimen\_Mutair](https://community.homey.app/u/Aimen_Mutair)\
**Post date:** [November 4, 2026, 6:48am UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/627 "2026-11-04T06:48:04Z")

</div>

Hi

I wanted to report an issue following the latest update regarding zone labeling and discovery:

1. **Zone Labeling:** I can no longer label new zones or add any new ones. While the labeling option appears under “Repair,” it only shows existing zones, not new ones.

2. **Zone Discovery:** I created a new zone in the Aqara app for the FP2 sensor, but it is not being discovered or appearing as a sensor/zone in the integration.

Could you please look into this? Let me know if you need any logs or further details to help troubleshoot.

Thanks!

---

<div class="post-metadata">

**Author:** ![Don\_Brown](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/don_brown/32/120935_2.png) [@Don\_Brown](https://community.homey.app/u/Don_Brown)\
**Post date:** [November 4, 2026, 3:34pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/628 "2026-11-04T15:34:54Z")

</div>

> [@Martin\_Verbeek](#):
>
> When adding devices it will list more information on devices that are available or not available to pair, it also is designed such that you can leave it open, it will update regularly with newly discovered devices in the network.

Wow! This is a great change! I really appreciate the great new changes. It does tend to flash a lot like the refresh rate is maybe too fast? My regret is that it seems none of my Thread or WiFi devices appear to be able to pair.

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [November 4, 2026, 4:08pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/629 "2026-11-04T16:08:26Z")

</div>

I now list both unpairable and pairables, got too many questions, about devices not being showed while they are indeed non-pairable. Sometimes devices take long to show in mDNS, FP2 is one of those.

The flashing is strange (mobile or other device?). I do not have that on both mobile or desktop. The rate is 5s.

If you see discrepancies in expected pairable devices, being showed as non-pair, please open an issue and log some screenshots / logging.

Enjoy 🙂

---

<div class="post-metadata">

**Author:** ![richthetech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/richthetech/32/123116_2.png) [@richthetech](https://community.homey.app/u/richthetech)\
**Post date:** [November 5, 2026, 12:55am UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/630 "2026-11-05T00:55:33Z")

</div>

Having issues with your app.. I have had it installed and running for a while now. Recently I have had to restart the app once a day. It works for a while and then will randomly stop. The device in question is a switch that also has motion sensor on it. This has worked for the last year but now when I restart your app, I will get motion sensing initially and then it will no longer register any motion. Controlling the switch on and off through Homey still works, but none of the built-in sensors on the device work. They will report after your app is restarted, and then nothing.

A separate issue I am now encountering is I am unable to connect any of the same devices using the previous procedure I used before. Your app has changed so now it lists all the HomeKit over IP devices available. It shows it as being available. It asks to enter the HomeKit code and then press enter… but there is no enter!

 ![Screenshot 2026-11-04 at 5.26.36 PM](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/7/07bd06b60247ce8eec980da507733666ae3fb630.jpeg)

 ![Screenshot 2026-11-04 at 5.54.43 PM](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/9/39a4fc6525a5be9d6be971be489468273d93a6c2.png)

It successfully connects to HomeKit after a full reset of the device. And all sensors are active in Homekit

---

<div class="post-metadata">

**Author:** ![Don\_Brown](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/don_brown/32/120935_2.png) [@Don\_Brown](https://community.homey.app/u/Don_Brown)\
**Post date:** [November 5, 2026, 1:43am UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/631 "2026-11-05T01:43:52Z")

</div>

I have the same problem with trying to enter the HomeKit code.

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [November 5, 2026, 6:22am UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/632 "2026-11-05T06:22:33Z")

</div>

If it is an iphone and you do no see return, press the 123 and you should see return.

If Android there must be an enter key or arrow

---

<div class="post-metadata">

**Author:** ![Don\_Brown](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/don_brown/32/120935_2.png) [@Don\_Brown](https://community.homey.app/u/Don_Brown)\
**Post date:** [November 5, 2026, 12:34pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/633 "2026-11-05T12:34:37Z")

</div>

There is a check mark only. I tried that several times. It never moved off the screen to start pairing.

Sincerely,  
Don Brown

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [November 5, 2026, 1:15pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/634 "2026-11-05T13:15:50Z")

</div>

Android or iPhone?

---

<div class="post-metadata">

**Author:** ![Don\_Brown](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/don_brown/32/120935_2.png) [@Don\_Brown](https://community.homey.app/u/Don_Brown)\
**Post date:** [November 5, 2026, 1:40pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/635 "2026-11-05T13:40:43Z")

</div>

iPhone 15 Pro with iOS 27.2.

Homey is 13.5.3

Your app version is 1.9.0

Homey app on my iPhone is 10.1.3

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [November 5, 2026, 3:25pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/636 "2026-11-05T15:25:05Z")

</div>

I will change the behavior such that it just will try to pair when you have entered 8 numbers.

---

<div class="post-metadata">

**Author:** ![Don\_Brown](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/don_brown/32/120935_2.png) [@Don\_Brown](https://community.homey.app/u/Don_Brown)\
**Post date:** [November 5, 2026, 4:42pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/637 "2026-11-05T16:42:38Z")

</div>

Sounds perfect

Sincerely,  
Don Brown

---

<div class="post-metadata">

**Author:** ![theBart](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thebart/32/76734_2.png) [@theBart](https://community.homey.app/u/theBart)\
**Post date:** [November 8, 2026, 9:42am UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/638 "2026-11-08T09:42:46Z")

</div>

I have the same issue with Aqara FP2; need to restart HomeKit Controller at least once a day since installing version 3.3.7. I have now updated to test version 3.4.0, hoping that it will fix the issue.

---

<div class="post-metadata">

**Author:** ![Don\_Brown](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/don_brown/32/120935_2.png) [@Don\_Brown](https://community.homey.app/u/Don_Brown)\
**Post date:** [November 14, 2026, 4:51pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/639 "2026-11-14T16:51:24Z")

</div>

Hello Martin,

I know you haven’t had a chance to change the behavior of the BLE path in the app, yet. I wanted to update you on a couple of things.

1. If you accept the Homekit code after 8 digits, that fine, but another option might be to scan the code via the camera. Might be more work, so, don’t go out of your way.
2. I did find a work around. After dropping the air filter out of Apple Home, I brought the device into my office and paired it there through my PC. Using BLE, and a couple of tries, it works fine, mostly. See #3 below.
3. In using the flow cards, I get an error.

 ![Homey Air Filter - 2026-11-14 104702](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/2/e25f00721f8275f241b79b1a512577f3037e03c2.png)

I’m not sure if this is an app problem, or a Homey Problem or what. Here is the diagnostic, hope it helps. 9229c758-b4f8-4bd8-a4e4-ea740ee2ffcf  
4) The Air filter no longer is present in my Apple Home app. I may try to add it back via the Sleekpoint app, but, if you have a suggestion, I’m ready to hear it.

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [November 14, 2026, 5:07pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/640 "2026-11-14T17:07:30Z")

</div>

I am waiting a bit with BLE until Athom fixes my issue with multiple same services in a accessory.

Camera support for this is only avail with Athoms own Matter device implementation. I have looked at it.

Will check out log.

---

<div class="post-metadata">

**Author:** ![Don\_Brown](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/don_brown/32/120935_2.png) [@Don\_Brown](https://community.homey.app/u/Don_Brown)\
**Post date:** [November 14, 2026, 5:53pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/641 "2026-11-14T17:53:28Z")

</div>

Just a clarification. I wasn’t trying to do anything with a camera, the air filters don’t have that, at least not mine.

 ![Air Filter simple flow-2026-11-14 115143](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/7/3760b497193e3dc4458c10f2979dcea056af1050.png)

This is where I get the error, in testing this flow.

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [November 14, 2026, 5:59pm UTC](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520/642 "2026-11-14T17:59:22Z")

</div>

Was referring to number 1 in the list​😅

[Previous page](https://community.homey.app/t/app-pro-homekit-controller-for-a-better-homey/94520.md?page=30)
