# \[APP\]\[Pro\] HomeKit Controller voor Homey (NL) **URL:** \ **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:** 20\ **Page:** 23
**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:** [October 30, 2024, 10:13pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/453 "2024-10-30T22:13:34Z")
> [@Hermann\_Stengel](#): > > dacht ik ergens gelezen te hebben Bijna altijd staat de handleiding in de start post van app topics, Hermann. Hier dus ook 😉 ---
**Author:** ![Hermann\_Stengel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hermann_stengel/32/12501_2.png) [@Hermann\_Stengel](https://community.homey.app/u/Hermann_Stengel)\ **Post date:** [October 31, 2024, 7:26am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/454 "2024-10-31T07:26:56Z")
Dat had ik gedaan. Ik reset de boel en probeer het nog een s. ---
**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:** [October 31, 2024, 8:13am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/455 "2024-10-31T08:13:50Z")
Gebruik je aqara app op iOS? Je ziet de FP2 niet als de sensor al paired is. Doe GEEN factory reset van de FP2. Alleen een netwerk settings reset, hou de knop van de fp2 ingedrukt tot ie begint te knipperen en voeg opnieuw toe aan de aqara app Indien iOs even uit Home app verwijderen en dan zou de fp2 zichtbaar moeten zijn. Het kan soms even duren. ---
**Author:** ![Hermann\_Stengel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hermann_stengel/32/12501_2.png) [@Hermann\_Stengel](https://community.homey.app/u/Hermann_Stengel)\ **Post date:** [October 31, 2024, 9:08pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/456 "2024-10-31T21:08:04Z")
Nadat ik de reset had uitgevoerd probeerde ik hem aan Homey toe te voegen…geen PF2… Toen moest ik weg, kwam 3 uur later terug, probeerde het nog eens en \* Poefffff \* daar was 'ie ineens! Vervolgens werd de homekit code gevraagd, verschillende mogelijkheden geprobeerd maar geen werkte. Ik dacht, misschien moet ik een Apple account nemen, ik heb namelijk Android en toen zag ik per ongeluk ineens een 8 cijverige code op het apparaat… EUREKA! Bedankt voor het meedenken ---
**Author:** ![Benvo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/benvo/32/79462_2.png) [@Benvo](https://community.homey.app/u/Benvo)\ **Post date:** [November 1, 2024, 12:31pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/457 "2024-11-01T12:31:59Z")
Ik zou graag mijn Aqara camera’s en Netatmo deurbel willen toevoegen. Waar kan ik de HomeKit code vinden ? ---
**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 1, 2024, 1:12pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/458 "2024-11-01T13:12:49Z")
Dat hangt ervan af. Als de devices achter een eigen bridge zitten, dan is de bridge degene met de code. Eerst bridge toevoegen, daarna zie je de andere devices (dan heb je geen code meer nodig). Als ze zelf een code hebben wordt het even zoeken of google-en ---
**Author:** ![Benvo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/benvo/32/79462_2.png) [@Benvo](https://community.homey.app/u/Benvo)\ **Post date:** [November 1, 2024, 1:19pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/459 "2024-11-01T13:19:17Z")
Oké bedankt voor je reactie ---
**Author:** ![Benvo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/benvo/32/79462_2.png) [@Benvo](https://community.homey.app/u/Benvo)\ **Post date:** [November 1, 2024, 1:26pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/460 "2024-11-01T13:26:52Z")
Begrijp ik het goed dat de code die ingevoerd moet worden anders is dan de code die op de HomeKit sticker staat? ---
**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 1, 2024, 1:33pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/461 "2024-11-01T13:33:15Z")
dat zou niet zo moeten zijn. Met google-en bedoel ik waar de code staat op een apparaat ---
**Author:** ![Matthew\_Hoogendijk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/matthew_hoogendijk/32/113399_2.png) [@Matthew\_Hoogendijk](https://community.homey.app/u/Matthew_Hoogendijk)\ **Post date:** [November 2, 2024, 7:56am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/462 "2024-11-02T07:56:51Z")
Hey @Martin_Verbeek, Bedankt voor je effort om deze app te maken en hem door te ontwikkelen, wordt gewaardeerd! Het is mij gelukt om de Aqara Video Doorbell G4 d.m.v. de repeater toe te voegen. Nu zou ik graag het volgende scenario willen maken: - Een flow die getriggerd wordt als een bepaald persoon die is opgeslagen in face management voor de deur staat. Kan jij me misschien verder helpen? ---
**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 2, 2024, 12:10pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/463 "2024-11-02T12:10:48Z")
Dat soort dingen worden volgens mij niet via de Homekit interface doorgegeven, maar als je hem ooit aan Homekit hebt gehad en dat was een mogelijkheid, hoor ik het graag! Ik check het iig nog een keer. ---
**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:** [November 2, 2024, 7:15pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/464 "2024-11-02T19:15:53Z")
Wellicht is de [Faceplusplus app](https://community.homey.app/t/app-pro-face-face-recognition-for-homey/29058) interessant voor je. ---
**Author:** ![Matthew\_Hoogendijk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/matthew_hoogendijk/32/113399_2.png) [@Matthew\_Hoogendijk](https://community.homey.app/u/Matthew_Hoogendijk)\ **Post date:** [November 3, 2024, 8:12am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/465 "2024-11-03T08:12:57Z")
Met Homekit had ik inderdaad geen ervaringen voor deze functie. Ik gebruikte deze functie met IFTTT. Jammer is dat je daar maar 2 applets voor kan maken met de free subscription. Bedankt voor het checken in ieder geval! ---
**Author:** ![Matthew\_Hoogendijk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/matthew_hoogendijk/32/113399_2.png) [@Matthew\_Hoogendijk](https://community.homey.app/u/Matthew_Hoogendijk)\ **Post date:** [November 3, 2024, 8:13am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/466 "2024-11-03T08:13:28Z")
Top! Daar ga ik eens naar kijken ---
**Author:** ![Hasse\_Z](https://avatars.discourse-cdn.com/v4/letter/h/8edcca/32.png) [@Hasse\_Z](https://community.homey.app/u/Hasse_Z)\ **Post date:** [November 3, 2024, 7:46pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/467 "2024-11-03T19:46:36Z")
@Martin_Verbeek maak inmiddels een klein jaar gebruik van je app, waarvoor dank! Recent 2 extra FP2’s toegevoegd op zolder. Deze verliezen af en toe verbinding wat opgelost kan worden door het herstarten van de HC app. In de Aqara app zelf hebben ze nog wel verbinding. Als ik het goed begrijp ligt dit probleem bij Aqara en is hier (nog) geen oplossing voor. Is onderstaande flow een goed idee als workaround? Of juist niet? Of heb je een betere suggestie… 🙂 Alle FP2’s zijn up-to-date. ![Screenshot 2024-11-03 20.40.18](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/d/0d49544651199d54db83e51629a66a1966abe422.png) ---
**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, 2024, 9:26pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/468 "2024-11-03T21:26:42Z")
De aqara app connectie loopt niet via Homekit. Homekit is een aparte service en connectie op de FP2. Die wil wel eens haperen. ---
**Author:** ![Bazeloth](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bazeloth/32/79224_2.png) [@Bazeloth](https://community.homey.app/u/Bazeloth)\ **Post date:** [December 11, 2024, 12:07pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/469 "2024-12-11T12:07:26Z")
@Martin_Verbeek Versie: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/7/d7cfa4405f1037b92ffcf2545a7462746e2c610a.png) Dit event wordt niet meer getriggered lijkt 't. LuxKitchen stond op 0 terwijl het 1 uur smiddags is en dit heeft tot nu toe altijd gewerkt: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/8/48262dc8fd8add6e14ceda7dcc6b1f47f2f86ebd.png) Kan je dit bevestigen? Heb je iets van me nodig? Er zijn geen updates beschikbaar in de Aqara app. ---
**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:** [December 11, 2024, 2:59pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/470 "2024-12-11T14:59:52Z")
Niets gewijzigd op dit gebied. ---
**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:** [December 11, 2024, 3:00pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/471 "2024-12-11T15:00:46Z")
Als je zoiets hebt dan even de log uit de app naar me sturen. NIET via diagnostic report! ---
**Author:** ![Bazeloth](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bazeloth/32/79224_2.png) [@Bazeloth](https://community.homey.app/u/Bazeloth)\ **Post date:** [December 11, 2024, 4:17pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/472 "2024-12-11T16:17:45Z")
Hierbij de logs. Ik heb 3 aqara’s waarvan er 2 in gebruik zijn. Het gaat dus om de FP2-968B. Deel 1: ```auto undefined2024-12-11T16:13:10.932Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:13:10.931Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:13:10.904Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:13:10.903Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:13:07.779Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:13:07.775Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:13:07.774Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:12:40.890Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:12:40.889Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:12:40.825Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:12:40.823Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:12:37.722Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:12:37.722Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:12:37.721Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:12:10.806Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:12:10.806Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:12:10.776Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:12:10.775Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:12:07.691Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:12:07.691Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:12:07.690Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:11:40.807Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:11:40.806Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:11:40.761Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:11:40.759Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:11:37.650Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:11:37.650Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:11:37.650Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:11:10.711Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:11:10.711Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:11:10.682Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:11:10.679Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:11:07.598Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:11:07.597Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:11:07.597Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:10:40.719Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:10:40.718Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:10:40.665Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:10:40.663Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:10:37.543Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:10:37.543Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:10:37.542Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:10:10.665Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:10:10.664Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:10:10.622Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:10:10.615Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:10:07.479Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:10:07.478Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:10:07.477Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:09:40.557Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:09:40.556Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:09:40.538Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:09:40.535Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:09:37.413Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:09:37.412Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:09:37.412Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:09:23.939Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar alarm_motion2 2 Occupancy Zone 2 {"aid":1,"iid":2698,"value":1} 2024-12-11T16:09:22.928Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar alarm_motion0 0 Occupancy Zone 0 {"aid":1,"iid":2690,"value":1} 2024-12-11T16:09:10.494Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:09:10.494Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:09:10.457Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:09:10.455Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:09:07.380Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:09:07.380Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:09:07.380Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:08:40.512Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:08:40.511Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:08:40.441Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:08:40.439Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:08:37.307Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:08:37.307Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:08:37.306Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:08:10.409Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:08:10.409Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:08:10.361Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:08:10.359Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:08:07.251Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:08:07.251Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:08:07.250Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:07:40.341Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:07:40.341Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:07:40.312Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:07:40.311Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:07:37.196Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:07:37.196Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:07:37.194Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:07:24.293Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar measure_luminance null No name {"aid":1,"iid":2674,"value":5} 2024-12-11T16:07:10.253Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:07:10.252Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:07:10.232Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:07:10.231Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:07:07.132Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:07:07.132Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:07:07.132Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:06:40.225Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:06:40.225Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:06:40.185Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:06:40.183Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:06:37.078Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:06:37.077Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:06:37.077Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:06:16.132Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar alarm_motion2 2 Occupancy Zone 2 {"aid":1,"iid":2698,"value":0} 2024-12-11T16:06:14.992Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar alarm_motion0 0 Occupancy Zone 0 {"aid":1,"iid":2690,"value":0} 2024-12-11T16:06:10.169Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:06:10.168Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:06:10.138Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:06:10.135Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:06:06.984Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:06:06.984Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:06:06.983Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:05:43.745Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar alarm_motion2 2 Occupancy Zone 2 {"aid":1,"iid":2698,"value":1} 2024-12-11T16:05:42.746Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar alarm_motion0 0 Occupancy Zone 0 {"aid":1,"iid":2690,"value":1} 2024-12-11T16:05:40.083Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:05:40.082Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:05:40.025Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:05:40.023Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:05:36.932Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:05:36.932Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:05:36.932Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:05:10.055Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:05:10.055Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:05:10.009Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:05:10.007Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:05:06.877Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:05:06.876Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:05:06.876Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:04:39.979Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:04:39.978Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:04:39.929Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:04:39.927Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:04:36.812Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:04:36.812Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:04:36.811Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:04:09.896Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:04:09.896Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:04:09.850Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:04:09.847Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:04:06.741Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:04:06.741Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:04:06.740Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:03:39.829Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:03:39.829Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:03:39.800Z [log] Socket close 192.168.68.69 63545 ``` [Previous page](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007.md?page=22) [Next page](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007.md?page=24)