# \[APP\]\[Pro\] HomeKit Controller voor Homey (NL)

**URL:** <https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007>\
**Category:** Apps\
**Tags:** webapp, homey-pro, community-app\
**Created:** [October 27, 2023, 9:17pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007 "2023-10-27T21:17:43Z")\
**Posts on this page:** 9\
**Page:** 31

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [July 25, 2026, 11:45am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/616 "2026-07-25T11:45:59Z")

</div>

> [@Pieter\_Pessers](#):
>
> Soms wordt je naar een engelse forum gestuurd.

Dat is enkel als de taal categorie niet overeenkomt

> ![Screenshot_20260725_134411_Ecosia](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/a/aaeec1b6a686fe4baa290c9abb2117c527fec9dc.jpeg)

De meeste app topic zijn in het Engels idd, soms zijn ze in het Nederlands, zoals deze.

---

<div class="post-metadata">

**Author:** ![Jan\_Peters](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_peters/32/48190_2.png) [@Jan\_Peters](https://community.homey.app/u/Jan_Peters)\
**Post date:** [August 17, 2026, 8:44pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/617 "2026-08-17T20:44:50Z")

</div>

Hallo, ik wil mijn Aqara FP2 via HomeKit aan Homey koppelen. Ik ben nu zover dat ik de sensor te zien krijg in HomeKit met de vraag om door te gaan met de installatie. Dan moet ik de Pincode intoetsen. Ik heb dat geprobeerd met zowel de HomeKit app pincode, als de FP2 pincode. Op beide krijg ik een foutcode terug. Wat gaat er nu precies fout?  
Hierbij het meest recente deel van de log:

2026-08-17T16:49:28.977Z [err] [ManagerDrivers] [Driver:hapIP] pairing not successful Presence-Sensor-FP2-6A92.\_hap.\_tcp.local Cannot set properties of null (setting ‘errorCode’)

2026-08-17T16:49:28.976Z [err] \_requestClear Socket error 192.168.2.24 62552 ECONNREFUSED

2026-08-17T16:49:28.708Z [log] startPairing M2, M1 is

2026-08-17T16:49:28.706Z [log] startPairing M1

2026-08-17T16:49:28.706Z [log] startPairing Connection

2026-08-17T16:49:28.706Z [log] startPairing method 0 flags 2

2026-08-17T16:49:28.706Z [log] [ManagerDrivers] [Driver:hapIP] pairSetup

2026-08-17T16:48:56.525Z [err] [ManagerDrivers] [Driver:hapIP] pairing not successful Presence-Sensor-FP2-6A92.\_hap.\_tcp.local Cannot set properties of null (setting ‘errorCode’)

2026-08-17T16:48:56.524Z [err] \_requestClear Socket error 192.168.2.24 62552 ECONNREFUSED

2026-08-17T16:48:56.420Z [log] startPairing M2, M1 is

2026-08-17T16:48:56.418Z [log] startPairing M1

2026-08-17T16:48:56.417Z [log] startPairing Connection

2026-08-17T16:48:56.417Z [log] startPairing method 0 flags 2

2026-08-17T16:48:56.416Z [log] [ManagerDrivers] [Driver:hapIP] pairSetup

2026-08-17T16:48:40.860Z [log] [ManagerDrivers] [Driver:hapIP] ShowView Pincode {

fullName: ‘Presence-Sensor-FP2-6A92.\_hap.\_tcp.local’,

aid: ‘1’,

completedParts: [‘TXT’, ‘SRV’, ‘PTR’, ‘A’],

---

<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:** [August 28, 2026, 5:18pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/618 "2026-08-28T17:18:44Z")

</div>

Er staat een **test** versie op de store (3.0.0) met o.a.

Bluetooth LE support.  
Nieuwe custom views voor pairing van nieuwe devices  
Veranderingen die, naar ik hoop, leiden tot betere stabiliteit van de aangesloten devices.  
iets frissere look en feel van de device icons.

---

<div class="post-metadata">

**Author:** ![KroeT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kroet/32/172371_2.png) [@KroeT](https://community.homey.app/u/KroeT)\
**Post date:** [September 1, 2026, 2:57pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/619 "2026-09-01T14:57:24Z")

</div>

**Apparaat wordt niet gevonden bij zoeken, koppelen via Developer Tools werkt wél**

App-versie 2.2.9, driver `hapIP`.

**Probleem**

Ik heb een ATAG One Zone-thermostaat die alleen HomeKit spreekt. Ik heb hem  
netjes uit Apple Home verwijderd, zodat hij vrij was om te koppelen. Daarna in  
de app “HomeKit over IP” gekozen en gezocht: niets. Ook onder “HomeKit over  
Thread” niets.

Wat ik heb geprobeerd, zonder resultaat:

- de app opnieuw gestart, zodat hij vers zou zoeken
- de Home-app op mijn iPhone volledig afgesloten, voor het geval die de  
verbinding bezet hield
- gecontroleerd dat de thermostaat en Homey in hetzelfde netwerk zitten

Ondertussen zag de Home-app van Apple hem wél gewoon als beschikbaar apparaat.  
Het lag dus niet aan de thermostaat.

**Wat wél werkte:** koppelen via de Homey Developer Tools. Daar de pincode  
ingevoerd en hij werd toegevoegd — inclusief huidige temperatuur, instelbare  
streeftemperatuur en de standen uit/verwarmen/koelen/automatisch. Hij werkt nu  
prima. Het is dus puur het _zoeken_ in de app dat mijn apparaat niet oppikt.

**Technisch**

Alles hieronder is gemeten, niet aangenomen.

Het apparaat kondigt zich correct aan (`dns-sd -Z _hap._tcp local.`):

```auto
Remote Gw Thermo-XXXXXX._hap._tcp SRV 0 0 80 hap-276566.local.
TXT "c#=2" "ff=1" "id=5F:91:40:17:C9:6B"
     "md=ATAG ONE XXXXXXXC0000" "pv=1.1" "sf=1" "ci=2" "s#=1"

```

- `sf=1`, dus niet gekoppeld en beschikbaar om te koppelen
- `ci=2`, categorie Bridge
- thermostaat en Homey zitten in hetzelfde /24-subnet

Het HAP-eindpunt antwoordt zoals het hoort:

```auto
$ curl -i http://<ip>/accessories
HTTP/1.1 470 Connection Authorization Required
{"status":-70401}

```

En pair-setup M1 levert een geldige M2:

```auto
State = 2 PublicKey = 384 bytes (2 TLV-blokken) Salt = 16 bytes

```

**Mijn vermoeden: de poort.** Dit apparaat draait HAP op **poort 80**. Andere  
HomeKit-apparaten hier zitten op 8080 (Hue-bridge) en 49294 / 62208 (HomePods).  
Als er in de ontdekkingsstap ergens wordt aangenomen dat poort 80 gewone HTTP  
is en geen HAP, verklaart dat precies wat ik zie: koppelen werkt, zoeken niet.

Nog een detail dat anderen kan helpen: bij de eerste poging kreeg ik  
`pairSetup M2: Error: 7 => Attached to other controller`. TLV-fout 7 is in de  
HAP-specificatie `Busy` — er stond nog een koppelsessie open. Even wachten en  
opnieuw proberen loste het op. De melding “attached to other controller” kan  
dus op het verkeerde been zetten.

---

<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:** [September 1, 2026, 3:01pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/620 "2026-09-01T15:01:57Z")

</div>

Poort 80 is een vervelende. Daar gaat behalve HAP nog meer overheen. Test eens met versie 3.0 die in test staat

---

<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:** [September 4, 2026, 8:42am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/621 "2026-09-04T08:42:25Z")

</div>

Zijn er mensen die een beetje serieus met de test versie bezig zijn geweest? Ben met name benieuwd hoe jullie de stabiliteit, de nieuwe pairing interface, en natuurlijk BLE support, ervaren.

---

<div class="post-metadata">

**Author:** ![Rinus\_Hulsker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rinus_hulsker/32/177004_2.png) [@Rinus\_Hulsker](https://community.homey.app/u/Rinus_Hulsker)\
**Post date:** [September 29, 2026, 5:07am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/622 "2026-09-29T05:07:31Z")

</div>

Hallo, ik heb 2 aqara fp2’s op homey SHS waar ik erg blij mee ben. Deze werken met de app Homekit Controller.

Gister (28-09-26) kreeg ik een mail vanuit Athom waarin zij aangaven dat ze stoppen met Homekit Experiment. Weet iemand wat de gevolgen zijn van het stoppen met Homekit Experiment voor de app Homekit Controller (en dus in mijn geval de Aqara FP2?).

---

<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:** [September 29, 2026, 5:40am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/623 "2026-09-29T05:40:47Z")

</div>

Geen. Controller haalt homekit devices naar Homey. Homekit experiment maakt Homey devices beschikbaar voor Apple home

---

<div class="post-metadata">

**Author:** ![Kaoh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kaoh/32/9283_2.png) [@Kaoh](https://community.homey.app/u/Kaoh)\
**Post date:** [October 22, 2026, 11:03pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/624 "2026-10-22T23:03:35Z")

</div>

Ik probeer dit toevallig nu. Helaas loop ik vast

> 2026-10-22T22:59:14.802Z [log] Service went Inactive (Advertisement last seen \> 3 minutes) for: c1c3e060fdce  
> 2026-10-22T22:56:03.379Z [log] [ManagerDrivers] [Driver:hapBLE] Pairing session disconnect  
> 2026-10-22T22:56:00.963Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 2 pairable devices  
> 2026-10-22T22:55:54.849Z [log] [ManagerDrivers] [Driver:hapBLE] validate\_pincode result {  
> valid: false,  
> error: “Cannot read properties of undefined (reading ‘connect’)”  
> }  
> 2026-10-22T22:55:54.848Z [log] [ManagerDrivers] [Driver:hapBLE] pairSetup failed Cannot read properties of undefined (reading ‘connect’)  
> 2026-10-22T22:55:54.846Z [err] [ManagerDrivers] [Driver:hapBLE] getPairingMethod not successful c1c3e060fdce TypeError: Cannot read properties of undefined (reading ‘connect’)  
> at BLEClient.getPairingMethod (/app/lib/transport/ble/ble-client.js:287:35)  
> at HapBLEDriver.pairSetup (/app/drivers/hapBLE/driver.js:39:35)  
> at /app/drivers/hapBLE/driver.js:154:30  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5)  
> 2026-10-22T22:55:54.844Z [err] Error while getting pairing method TypeError: Cannot read properties of undefined (reading ‘connect’)  
> at BLEClient.getPairingMethod (/app/lib/transport/ble/ble-client.js:287:35)  
> at HapBLEDriver.pairSetup (/app/drivers/hapBLE/driver.js:39:35)  
> at /app/drivers/hapBLE/driver.js:154:30  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5)  
> 2026-10-22T22:55:54.842Z [err] [ManagerDrivers] [Driver:hapBLE] BLEClient onInit not successful peripheralUuid: c1c3e060fdce Error: Peripheral Not Found: c1c3e060fdce  
> at Remote Process  
> at HomeyClient.emit (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)  
> at ManagerBLE.find (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/manager/ble.js:130:47)  
> at BLEClient.onInit (/app/lib/transport/ble/ble-client.js:80:55)  
> at /app/drivers/hapBLE/driver.js:145:17  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5) {  
> statusCode: 404  
> }  
> 2026-10-22T22:55:54.842Z [log] Initial BLE connection failed: Peripheral Not Found: c1c3e060fdce  
> 2026-10-22T22:55:54.839Z [log] Txt: {  
> ff: 1,  
> id: ‘b50846136325’,  
> ci: 5,  
> ‘s#’: 1,  
> pv: ‘1.0’,  
> sf: 0,  
> ‘c#’: 1,  
> mf: ‘4C’,  
> cv: 2,  
> sh: ‘fMS6Lw==’,  
> type: 6,  
> subtype: 49,  
> aid: 1,  
> class: ‘light’,  
> availableToPair: true,  
> pairMethod: 1  
> }  
> 2026-10-22T22:55:54.838Z [log] INITIAL SERVICEUP EMIT FOR eb5e9cc60336  
> 2026-10-22T22:55:54.837Z [log] BLE Advertisement Scanner found service: eb5e9cc60336 rssi -53 with updated Signal Strength Excellent and last seen 2026-10-22T22:55:54.831Z  
> 2026-10-22T22:55:54.832Z [err] [ManagerDrivers] [Driver:hapBLE] Failed to find advertisement for peripheralUuid: c1c3e060fdce Error: Peripheral Not Found: c1c3e060fdce  
> at Remote Process  
> at HomeyClient.emit (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)  
> at ManagerBLE.find (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/manager/ble.js:130:47)  
> at /app/drivers/hapBLE/driver.js:140:47  
> at PairSession.\_triggerEvent (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/PairSession.js:80:12)  
> at ManagerDrivers.\_onPairSessionEvent (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/manager/drivers.js:190:20)  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5) {  
> statusCode: 404  
> }  
> 2026-10-22T22:55:50.924Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:55:49.561Z [log] [ManagerDrivers] [Driver:hapBLE] Received payload validation request: 022-26-369  
> 2026-10-22T22:55:49.507Z [log] [ManagerDrivers] [Driver:hapBLE] frontend\_log: Submitting pincode: 022-26-369  
> 2026-10-22T22:55:40.915Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:55:24.789Z [log] [MyApp] cpu warning { count: 1, limit: 12 }  
> 2026-10-22T22:55:18.092Z [log] MDNS Scanner ready and querying for \_hap.\_tcp/\_udp.local services.  
> 2026-10-22T22:55:15.065Z [log] [CoAP UDP6] Socket is listening on [::]:5683  
> 2026-10-22T22:55:15.064Z [log] [CoAP UDP6] Unicast Server securely bound to port 5683 on all IPv6 interfaces (‘::’)  
> 2026-10-22T22:55:15.061Z [log] [ManagerDrivers] [Driver:hapThread] hapThread driver has been initialized  
> 2026-10-22T22:55:15.055Z [log] [ManagerDrivers] [Driver:hapIP] hapIP driver has been initialized  
> 2026-10-22T22:55:15.054Z [log] [ManagerDrivers] [Driver:hapBLE] hapBLE driver has been initialized  
> 2026-10-22T22:55:14.896Z [log] [ManagerDrivers] [Driver:hapBLE] HapBLE driver is initialized   
> 2026-10-22T22:55:14.877Z [log] Txt: {  
> ff: 1,  
> id: ‘7362e8088ecf’,  
> ci: 5,  
> ‘s#’: 1,  
> pv: ‘1.0’,  
> sf: 0,  
> ‘c#’: 1,  
> mf: ‘4C’,  
> cv: 2,  
> sh: ‘1FrZ1A==’,  
> type: 6,  
> subtype: 49,  
> aid: 1,  
> class: ‘light’,  
> availableToPair: true,  
> pairMethod: 1  
> }  
> 2026-10-22T22:55:14.875Z [log] INITIAL SERVICEUP EMIT FOR c1c3e060fdce  
> 2026-10-22T22:55:14.874Z [log] BLE Advertisement Scanner found service: c1c3e060fdce rssi -45 with updated Signal Strength Excellent and last seen 2026-10-22T22:55:14.860Z  
> 2026-10-22T22:55:14.860Z [log] Homey IP addresses detected as [‘127.0.0.1’, ‘192.168.3.54’]  
> 2026-10-22T22:55:14.809Z [log] [MyApp] Homekit Controller 3.2.8 has been initialized, nodejs version 22.23.2  
> 2026-10-22T22:55:14.793Z [log] Starting BLE Advertisement Scanner  
> 2026-10-22T22:55:14.787Z [log] Starting MDNS Scanner  
> 2026-10-22T22:55:14.786Z [log] capturing stderr  
> 2026-10-22T22:55:14.784Z [log] capturing stdout  
> 2026-10-22T22:55:13.638Z [log] BLE Advertisement Scanner closed.  
> 2026-10-22T22:55:13.637Z [log] MDNS Scanner closed.  
> 2026-10-22T22:55:13.634Z [log] [MyApp] app unload called  
> 2026-10-22T22:55:12.645Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 2 pairable devices  
> 2026-10-22T22:55:02.641Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 2 pairable devices  
> 2026-10-22T22:54:52.640Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 2 pairable devices  
> 2026-10-22T22:54:42.640Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 2 pairable devices  
> 2026-10-22T22:54:32.638Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 2 pairable devices  
> 2026-10-22T22:54:25.626Z [log] [ManagerDrivers] [Driver:hapBLE] validate\_pincode result {  
> valid: false,  
> error: “Cannot read properties of undefined (reading ‘connect’)”  
> }  
> 2026-10-22T22:54:25.625Z [log] [ManagerDrivers] [Driver:hapBLE] pairSetup failed Cannot read properties of undefined (reading ‘connect’)  
> 2026-10-22T22:54:25.625Z [err] [ManagerDrivers] [Driver:hapBLE] getPairingMethod not successful d6d8df7a9468 TypeError: Cannot read properties of undefined (reading ‘connect’)  
> at BLEClient.getPairingMethod (/app/lib/transport/ble/ble-client.js:287:35)  
> at HapBLEDriver.pairSetup (/app/drivers/hapBLE/driver.js:39:35)  
> at /app/drivers/hapBLE/driver.js:154:30  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5)  
> 2026-10-22T22:54:25.623Z [err] Error while getting pairing method TypeError: Cannot read properties of undefined (reading ‘connect’)  
> at BLEClient.getPairingMethod (/app/lib/transport/ble/ble-client.js:287:35)  
> at HapBLEDriver.pairSetup (/app/drivers/hapBLE/driver.js:39:35)  
> at /app/drivers/hapBLE/driver.js:154:30  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5)  
> 2026-10-22T22:54:25.622Z [err] [ManagerDrivers] [Driver:hapBLE] BLEClient onInit not successful peripheralUuid: d6d8df7a9468 Error: Peripheral Not Found: d6d8df7a9468  
> at Remote Process  
> at HomeyClient.emit (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)  
> at ManagerBLE.find (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/manager/ble.js:130:47)  
> at BLEClient.onInit (/app/lib/transport/ble/ble-client.js:80:55)  
> at /app/drivers/hapBLE/driver.js:145:17  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5) {  
> statusCode: 404  
> }  
> 2026-10-22T22:54:25.621Z [log] Initial BLE connection failed: Peripheral Not Found: d6d8df7a9468  
> 2026-10-22T22:54:25.616Z [err] [ManagerDrivers] [Driver:hapBLE] Failed to find advertisement for peripheralUuid: d6d8df7a9468 Error: Peripheral Not Found: d6d8df7a9468  
> at Remote Process  
> at HomeyClient.emit (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)  
> at ManagerBLE.find (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/manager/ble.js:130:47)  
> at /app/drivers/hapBLE/driver.js:140:47  
> at PairSession.\_triggerEvent (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/PairSession.js:80:12)  
> at ManagerDrivers.\_onPairSessionEvent (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/manager/drivers.js:190:20)  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5) {  
> statusCode: 404  
> }  
> 2026-10-22T22:54:22.636Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 2 pairable devices  
> 2026-10-22T22:54:15.502Z [log] [ManagerDrivers] [Driver:hapBLE] Received payload validation request: 022-26-369  
> 2026-10-22T22:54:15.467Z [log] [ManagerDrivers] [Driver:hapBLE] frontend\_log: Submitting pincode: 022-26-369  
> 2026-10-22T22:54:12.676Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 2 pairable devices  
> 2026-10-22T22:54:03.247Z [log] [ManagerDrivers] [Driver:hapBLE] validate\_pincode result {  
> valid: false,  
> error: “Cannot read properties of undefined (reading ‘connect’)”  
> }  
> 2026-10-22T22:54:03.247Z [log] [ManagerDrivers] [Driver:hapBLE] pairSetup failed Cannot read properties of undefined (reading ‘connect’)  
> 2026-10-22T22:54:03.247Z [err] [ManagerDrivers] [Driver:hapBLE] getPairingMethod not successful d6d8df7a9468 TypeError: Cannot read properties of undefined (reading ‘connect’)  
> at BLEClient.getPairingMethod (/app/lib/transport/ble/ble-client.js:287:35)  
> at HapBLEDriver.pairSetup (/app/drivers/hapBLE/driver.js:39:35)  
> at /app/drivers/hapBLE/driver.js:154:30  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5)  
> 2026-10-22T22:54:03.246Z [err] Error while getting pairing method TypeError: Cannot read properties of undefined (reading ‘connect’)  
> at BLEClient.getPairingMethod (/app/lib/transport/ble/ble-client.js:287:35)  
> at HapBLEDriver.pairSetup (/app/drivers/hapBLE/driver.js:39:35)  
> at /app/drivers/hapBLE/driver.js:154:30  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5)  
> 2026-10-22T22:54:03.244Z [err] [ManagerDrivers] [Driver:hapBLE] BLEClient onInit not successful peripheralUuid: d6d8df7a9468 Error: Peripheral Not Found: d6d8df7a9468  
> at Remote Process  
> at HomeyClient.emit (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)  
> at ManagerBLE.find (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/manager/ble.js:130:47)  
> at BLEClient.onInit (/app/lib/transport/ble/ble-client.js:80:55)  
> at /app/drivers/hapBLE/driver.js:145:17  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5) {  
> statusCode: 404  
> }  
> 2026-10-22T22:54:03.244Z [log] Initial BLE connection failed: Peripheral Not Found: d6d8df7a9468  
> 2026-10-22T22:54:03.239Z [err] [ManagerDrivers] [Driver:hapBLE] Failed to find advertisement for peripheralUuid: d6d8df7a9468 Error: Peripheral Not Found: d6d8df7a9468  
> at Remote Process  
> at HomeyClient.emit (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)  
> at ManagerBLE.find (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/manager/ble.js:130:47)  
> at /app/drivers/hapBLE/driver.js:140:47  
> at PairSession.\_triggerEvent (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/PairSession.js:80:12)  
> at ManagerDrivers.\_onPairSessionEvent (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/manager/drivers.js:190:20)  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5) {  
> statusCode: 404  
> }  
> 2026-10-22T22:54:03.238Z [log] Txt: {  
> ff: 1,  
> id: ‘7362e8088ecf’,  
> ci: 5,  
> ‘s#’: 1,  
> pv: ‘1.0’,  
> sf: 0,  
> ‘c#’: 1,  
> mf: ‘4C’,  
> cv: 2,  
> sh: ‘1FrZ1A==’,  
> type: 6,  
> subtype: 49,  
> aid: 1,  
> class: ‘light’,  
> availableToPair: true,  
> pairMethod: 1  
> }  
> 2026-10-22T22:54:03.238Z [log] INITIAL SERVICEUP EMIT FOR c1c3e060fdce  
> 2026-10-22T22:54:03.237Z [log] BLE Advertisement Scanner found service: c1c3e060fdce rssi -57 with updated Signal Strength Excellent and last seen 2026-10-22T22:54:03.236Z  
> 2026-10-22T22:54:02.631Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:53:58.597Z [log] [ManagerDrivers] [Driver:hapBLE] Received payload validation request: 022-26-369  
> 2026-10-22T22:53:58.561Z [log] [ManagerDrivers] [Driver:hapBLE] frontend\_log: Submitting pincode: 022-26-369  
> 2026-10-22T22:53:52.631Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:53:42.631Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:53:41.329Z [log] [ManagerDrivers] [Driver:hapBLE] validate\_pincode result {  
> valid: false,  
> error: “Cannot read properties of undefined (reading ‘connect’)”  
> }  
> 2026-10-22T22:53:41.329Z [log] [ManagerDrivers] [Driver:hapBLE] pairSetup failed Cannot read properties of undefined (reading ‘connect’)  
> 2026-10-22T22:53:41.329Z [err] [ManagerDrivers] [Driver:hapBLE] getPairingMethod not successful d6d8df7a9468 TypeError: Cannot read properties of undefined (reading ‘connect’)  
> at BLEClient.getPairingMethod (/app/lib/transport/ble/ble-client.js:287:35)  
> at HapBLEDriver.pairSetup (/app/drivers/hapBLE/driver.js:39:35)  
> at /app/drivers/hapBLE/driver.js:154:30  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5)  
> 2026-10-22T22:53:41.328Z [err] Error while getting pairing method TypeError: Cannot read properties of undefined (reading ‘connect’)  
> at BLEClient.getPairingMethod (/app/lib/transport/ble/ble-client.js:287:35)  
> at HapBLEDriver.pairSetup (/app/drivers/hapBLE/driver.js:39:35)  
> at /app/drivers/hapBLE/driver.js:154:30  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5)  
> 2026-10-22T22:53:41.327Z [err] [ManagerDrivers] [Driver:hapBLE] BLEClient onInit not successful peripheralUuid: d6d8df7a9468 Error: Could not connect to peripheral d6d8df7a9468  
> at Remote Process  
> at HomeyClient.emit (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)  
> at Object.emit (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/manager/ble.js:243:32)  
> at /app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/BlePeripheral.js:108:21  
> at new Promise ()  
> at BlePeripheral.connect (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/BlePeripheral.js:107:12)  
> at BleAdvertisement.connect (/app/packages/homey-local/lib/AppProcess/node\_modules/@athombv/homey-apps-sdk-v3/lib/BleAdvertisement.js:99:30)  
> at BLEClient.onInit (/app/lib/transport/ble/ble-client.js:81:57)  
> at process.processTicksAndRejections (node:internal/process/task\_queues:103:5)  
> at async /app/drivers/hapBLE/driver.js:145:4  
> 2026-10-22T22:53:41.326Z [log] Initial BLE connection failed: Could not connect to peripheral d6d8df7a9468  
> 2026-10-22T22:53:32.629Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:53:22.625Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:53:20.724Z [log] [ManagerDrivers] [Driver:hapBLE] Received payload validation request: 022-26-369  
> 2026-10-22T22:53:20.692Z [log] [ManagerDrivers] [Driver:hapBLE] frontend\_log: Submitting pincode: 022-26-369  
> 2026-10-22T22:53:12.618Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:53:11.342Z [log] [ManagerDrivers] [Driver:hapBLE] Pairing session disconnect  
> 2026-10-22T22:53:05.466Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:52:55.465Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:52:45.465Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:52:35.464Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:52:25.462Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:52:15.460Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:52:05.458Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:51:55.458Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:51:45.457Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:51:35.454Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:51:25.454Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:51:19.919Z [log] [ManagerDrivers] [Driver:hapBLE] validate\_pincode result { valid: false, error: ‘Operation failed with ATT error: 0x0e’ }  
> 2026-10-22T22:51:19.915Z [log] [ManagerDrivers] [Driver:hapBLE] pairSetup failed Operation failed with ATT error: 0x0e  
> 2026-10-22T22:51:19.915Z [err] [ManagerDrivers] [Driver:hapBLE] pairing not successful d6d8df7a9468 undefined  
> 2026-10-22T22:51:16.500Z [log] d6d8df7a9468 Start Pair process …  
> 2026-10-22T22:51:16.499Z [log] [ManagerDrivers] [Driver:hapBLE] pairSetup 022-26-369 0  
> 2026-10-22T22:51:15.453Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:51:15.379Z [log] [ManagerDrivers] [Driver:hapBLE] BLEClient onInit successful peripheralUuid: d6d8df7a9468  
> 2026-10-22T22:51:15.231Z [log] [ManagerDrivers] [Driver:hapBLE] Received payload validation request: 022-26-369  
> 2026-10-22T22:51:15.188Z [log] [ManagerDrivers] [Driver:hapBLE] frontend\_log: Submitting pincode: 022-26-369  
> 2026-10-22T22:51:09.434Z [log] [ManagerDrivers] [Driver:hapBLE] validate\_pincode result { valid: false, error: ‘Operation failed with ATT error: 0x0e’ }  
> 2026-10-22T22:51:09.427Z [log] [ManagerDrivers] [Driver:hapBLE] pairSetup failed Operation failed with ATT error: 0x0e  
> 2026-10-22T22:51:09.425Z [err] [ManagerDrivers] [Driver:hapBLE] pairing not successful d6d8df7a9468 undefined  
> 2026-10-22T22:51:06.155Z [log] d6d8df7a9468 Start Pair process …  
> 2026-10-22T22:51:06.153Z [log] [ManagerDrivers] [Driver:hapBLE] pairSetup 022-26-369 0  
> 2026-10-22T22:51:05.452Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:50:58.893Z [log] [ManagerDrivers] [Driver:hapBLE] BLEClient onInit successful peripheralUuid: d6d8df7a9468  
> 2026-10-22T22:50:55.450Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:50:48.229Z [log] [ManagerDrivers] [Driver:hapBLE] Received payload validation request: 022-26-369  
> 2026-10-22T22:50:48.179Z [log] [ManagerDrivers] [Driver:hapBLE] frontend\_log: Submitting pincode: 022-26-369  
> 2026-10-22T22:50:45.450Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:50:35.450Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:50:25.437Z [log] [ManagerDrivers] [Driver:hapBLE] getDevicelist found 1 pairable devices  
> 2026-10-22T22:50:03.239Z [log] Txt: {  
> ff: 1,  
> id: ‘05b5cd75c92e’,  
> ci: 5,  
> ‘s#’: 1,  
> pv: ‘1.0’,  
> sf: 0,  
> ‘c#’: 1,  
> mf: ‘4C’,  
> cv: 2,  
> sh: ‘yI9DSw==’,  
> type: 6,  
> subtype: 49,  
> aid: 1,  
> class: ‘light’,  
> availableToPair: true,  
> pairMethod: 1  
> }  
> 2026-10-22T22:50:03.239Z [log] INITIAL SERVICEUP EMIT FOR d6d8df7a9468  
> 2026-10-22T22:50:03.237Z [log] BLE Advertisement Scanner found service: d6d8df7a9468 rssi -56 with updated Signal Strength Excellent and last seen 2026-10-22T22:50:03.232Z  
> 2026-10-22T22:50:03.188Z [log] [MyApp] cpu warning { count: 1, limit: 12 }  
> 2026-10-22T22:49:56.543Z [log] MDNS Scanner ready and querying for \_hap.\_tcp/\_udp.local services.  
> 2026-10-22T22:49:53.484Z [log] [ManagerDrivers] [Driver:hapIP] hapIP driver has been initialized  
> 2026-10-22T22:49:53.483Z [log] [CoAP UDP6] Socket is listening on [::]:5683  
> 2026-10-22T22:49:53.482Z [log] [CoAP UDP6] Unicast Server securely bound to port 5683 on all IPv6 interfaces (‘::’)  
> 2026-10-22T22:49:53.472Z [log] [ManagerDrivers] [Driver:hapThread] hapThread driver has been initialized  
> 2026-10-22T22:49:53.454Z [log] [ManagerDrivers] [Driver:hapBLE] hapBLE driver has been initialized  
> 2026-10-22T22:49:53.441Z [log] Homey IP addresses detected as [‘127.0.0.1’, ‘192.168.3.54’]  
> 2026-10-22T22:49:53.288Z [log] [ManagerDrivers] [Driver:hapBLE] HapBLE driver is initialized   
> 2026-10-22T22:49:53.209Z [log] [MyApp] Homekit Controller 3.2.8 has been initialized, nodejs version 22.23.2  
> 2026-10-22T22:49:53.192Z [log] Starting BLE Advertisement Scanner  
> 2026-10-22T22:49:53.190Z [log] Starting MDNS Scanner  
> 2026-10-22T22:49:53.189Z [log] capturing stderr  
> 2026-10-22T22:49:53.187Z [log] capturing stdout  
> 2026-10-22T22:49:51.308Z [log] MDNS Scanner closed.  
> 2026-10-22T22:49:51.306Z [log] [MyApp] app unload called  
> 2026-10-22T22:47:03.896Z [log] [ManagerDrivers] [Driver:hapThread] list\_devices   
> 2026-10-22T22:47:03.896Z [log] getMDNSPairableDevices for udp   
> 2026-10-22T22:46:58.413Z [log] [ManagerDrivers] [Driver:hapThread] list\_devices   
> 2026-10-22T22:46:58.413Z [log] getMDNSPairableDevices for udp   
> 2026-10-22T22:46:53.213Z [log] [ManagerDrivers] [Driver:hapThread] list\_devices   
> 2026-10-22T22:46:53.213Z [log] getMDNSPairableDevices for udp   
> 2026-10-22T22:46:47.305Z [log] [ManagerDrivers] [Driver:hapThread] list\_devices   
> 2026-10-22T22:46:47.304Z [log] getMDNSPairableDevices for udp   
> 2026-10-22T22:46:40.621Z [log] [ManagerDrivers] [Driver:hapThread] list\_devices   
> 2026-10-22T22:46:40.619Z [log] getMDNSPairableDevices for udp   
> 2026-10-22T22:35:38.981Z [log] [ManagerDrivers] [Driver:hapThread] list\_devices   
> 2026-10-22T22:35:38.980Z [log] getMDNSPairableDevices for udp   
> 2026-10-22T22:35:32.730Z [log] pairing found devices:   
> 2026-10-22T22:35:32.729Z [log] getMDNSPairableDevices for tcp   
> 2026-10-22T22:35:25.819Z [log] [ManagerDrivers] [Driver:hapThread] list\_devices   
> 2026-10-22T22:35:25.818Z [log] getMDNSPairableDevices for udp   
> 2026-10-22T22:18:57.742Z [log] [MyApp] cpu warning { count: 1, limit: 12 }  
> 2026-10-22T22:18:51.033Z [log] MDNS Scanner ready and querying for \_hap.\_tcp/\_udp.local services.  
> 2026-10-22T22:18:49.945Z [log] [ManagerDrivers] [Driver:hapThread] list\_devices   
> 2026-10-22T22:18:49.944Z [log] getMDNSPairableDevices for udp   
> 2026-10-22T22:18:47.996Z [log] [ManagerDrivers] [Driver:hapThread] hapThread driver has been initialized  
> 2026-10-22T22:18:47.985Z [log] [ManagerDrivers] [Driver:hapIP] checkPairData remaining pairData:   
> 2026-10-22T22:18:47.985Z [log] [ManagerDrivers] [Driver:hapIP] checkPairData pairedDevices:   
> 2026-10-22T22:18:47.984Z [log] [ManagerDrivers] [Driver:hapIP] hapIP driver has been initialized  
> 2026-10-22T22:18:47.973Z [log] Homey IP addresses detected as [‘127.0.0.1’, ‘192.168.3.54’]  
> 2026-10-22T22:18:47.768Z [log] [MyApp] Homekit Controller 2.2.9 has been initialized  
> 2026-10-22T22:18:47.751Z [log] Starting MDNS Scanner  
> 2026-10-22T22:18:47.750Z [log] capturing stderr  
> 2026-10-22T22:18:47.744Z [log] capturing stdout

 ![91](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/9/39eae796bc9754c314f30bfd4888a5010c430a48.png)

Zou geweldig zijn als deze het gaan doen, was ooit een miskoop omdat ik alleen thread had gelezen en ik geen Apple spul heb kon ik er niet veel mee

[Previous page](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007.md?page=30)