# \[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:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![Valentin\_Ciopei](https://avatars.discourse-cdn.com/v4/letter/v/6bbea6/32.png) [@Valentin\_Ciopei](https://community.homey.app/u/Valentin_Ciopei)\
**Post date:** [November 3, 2023, 12:02pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/42 "2023-11-03T12:02:05Z")

</div>

App not reliable yet?  
It seems that room occupancy remains ON until app is restarted. Same when I get back in the room.

---

<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, 2023, 12:42pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/43 "2023-11-03T12:42:32Z")

</div>

Not at my home… ghosting?

---

<div class="post-metadata">

**Author:** ![Valentin\_Ciopei](https://avatars.discourse-cdn.com/v4/letter/v/6bbea6/32.png) [@Valentin\_Ciopei](https://community.homey.app/u/Valentin_Ciopei)\
**Post date:** [November 3, 2023, 1:13pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/44 "2023-11-03T13:13:52Z")

</div>

Nope. In the Aqara app everything is OK and in Homey, the values of the sensor are updated only when I restart the app.

I also tested the light sensor

 ![Screenshot 2023-11-03 at 15.39.23](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/2/b2f1959386ba114c5ce61a76067623910a30d034.png)

4692bd5b-df98-4bac-b39f-1a427d88ace8

* * *

Update: I restarted the app once more and I did some tests. It works now.  
I also created a flow to monitor if the app crashes.

---

<div class="post-metadata">

**Author:** ![Valentin\_Ciopei](https://avatars.discourse-cdn.com/v4/letter/v/6bbea6/32.png) [@Valentin\_Ciopei](https://community.homey.app/u/Valentin_Ciopei)\
**Post date:** [November 3, 2023, 2:34pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/45 "2023-11-03T14:34:30Z")

</div>

App works only few minutes after restart.  
The “App xxx has crashed” flow doesn’t detect anything.

---

<div class="post-metadata">

**Author:** ![jevvol](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jevvol/32/34198_2.png) [@jevvol](https://community.homey.app/u/jevvol)\
**Post date:** [November 3, 2023, 3:25pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/46 "2023-11-03T15:25:23Z")

</div>

Hi. Nice job.  
Can you add support for vocolinc humidifier?

---

<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, 2023, 3:51pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/47 "2023-11-03T15:51:30Z")

</div>

Weird … I do not see a crash in the app dashboard either…

Just hang on a bit until logging is released…

---

<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, 2023, 8:19pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/48 "2023-11-03T20:19:44Z")

</div>

for some reason the FP2 it disconnects from the network…resubscribe does not work, are you changing zone definitions in the FP2?

192.168.1.36:63003 Persistent connection client got disconnected  
2023-11-03T12:08:17.527Z [log] [ManagerDrivers] [Driver:hapIP] [Device:31e095fe-b9fd-41d7-81e7-7299e3bfd87e] listenToEvents Disconnected: network connect will resubscribe  
2023-11-03T12:08:17.528Z [log] [ManagerDrivers] [Driver:hapIP] [Device:31e095fe-b9fd-41d7-81e7-7299e3bfd87e] listenToEvents unsubscribe succes

---

<div class="post-metadata">

**Author:** ![Valentin\_Ciopei](https://avatars.discourse-cdn.com/v4/letter/v/6bbea6/32.png) [@Valentin\_Ciopei](https://community.homey.app/u/Valentin_Ciopei)\
**Post date:** [November 3, 2023, 8:54pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/49 "2023-11-03T20:54:27Z")

</div>

Maybe that is when I restarted the sensor?  
Local network seems stable and the FP2 has a reserved IP address.

Also I’m not using zones. sensor is in my office and is not big enough to use zones.

 ![Screenshot 2023-11-03 at 22.54.10](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/f/7f4fb7f40a0458d601e3aa8b515e250964ea44bf.png)

---

<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, 2023, 10:13pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/50 "2023-11-03T22:13:40Z")

</div>

Then it will surely disconnect. The issue is the the FP2 will use the same IP but a different port. And Homeys discovery does not show the new port when the app runs, it only gets that when you reinit the app

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [November 4, 2023, 6:27am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/51 "2023-11-04T06:27:54Z")

</div>

> [@Martin\_Verbeek](#):
>
> And Homeys discovery does not show the new port when the app runs, it only gets that when you reinit the app

Perhaps add a comment to [MDNS discovery not having updated txt or port on lastseen events · Issue #322 · athombv/homey-apps-sdk-issues · GitHub](https://github.com/athombv/homey-apps-sdk-issues/issues/322)

---

<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, 2023, 7:30am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/52 "2023-11-04T07:30:01Z")

</div>

That’s me opening the issue…

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [November 4, 2023, 7:30am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/53 "2023-11-04T07:30:52Z")

</div>

Whoops 😅

---

<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, 2023, 8:10am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/54 "2023-11-04T08:10:33Z")

</div>

Is there a way around using standard discovery from Athom? Tried other package but i guess the Homey environment does not allow for apps to do this themselves…

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [November 4, 2023, 8:31am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/55 "2023-11-04T08:31:51Z")

</div>

Did a little test with [`bonjour`](https://github.com/watson/bonjour) and it finds all my HomeKit devices just fine.

---

<div class="post-metadata">

**Author:** ![Mike\_de\_Vries](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike_de_vries/32/109113_2.png) [@Mike\_de\_Vries](https://community.homey.app/u/Mike_de_Vries)\
**Post date:** [November 4, 2023, 12:41pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/56 "2023-11-04T12:41:54Z")

</div>

Even in NL:

Het ziet er naar uit dat de kaartjes helderheid groter dan, helderheid kleiner dan, omgedraaid zijn.  
Dus kleiner dan is eigenlijk groter dan en omgekeerd.

Mijn flow deed het niet en na het omdraaien van de waardes werkte het wel.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/6/d672698a9ff1269a779b4ffed3dbcbec649208d4.png)

---

<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, 2023, 1:02pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/57 "2023-11-04T13:02:16Z")

</div>

Daar doe ik eigenlijk niets aan, standaard door Homey gemaakt. Ga later checken waarom dit gebeurd…

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [November 4, 2023, 1:38pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/58 "2023-11-04T13:38:30Z")

</div>

Helderheid werkt bij mij wel volgens verwachting in v0.0.3.

Ik heb wel een wens: de helderheid ook als EN voorwaarde in een advanced flow kunnen definieren. Voorbeeld: als de zone wordt betreden EN het is minder dan 75 lux, doe de lamp aan.

---

<div class="post-metadata">

**Author:** ![Marcel\_Visser](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcel_visser/32/66024_2.png) [@Marcel\_Visser](https://community.homey.app/u/Marcel_Visser)\
**Post date:** [November 4, 2023, 2:36pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/59 "2023-11-04T14:36:36Z")

</div>

Dat moet middels een logica kaartje mogelijk zijn.

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [November 4, 2023, 9:10pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/60 "2023-11-04T21:10:55Z")

</div>

I would like to make an advanced flow to prevent blinking lights with the FP2. For example: if x seconds after leaving a zone the zone is still not occupied, turn off the lights, otherwise keep lights on.  
Anybody an example or solution how to define this?

---

<div class="post-metadata">

**Author:** ![Valentin\_Ciopei](https://avatars.discourse-cdn.com/v4/letter/v/6bbea6/32.png) [@Valentin\_Ciopei](https://community.homey.app/u/Valentin_Ciopei)\
**Post date:** [November 5, 2023, 4:21am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/61 "2023-11-05T04:21:00Z")

</div>

This works  
 ![Screenshot 2023-11-05 at 06.20.35](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/4/f4df037fd713b62f6c8fdf9d6b309f1b256f8b02.png)

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

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