# \[App\]\[Pro\] HomeKitty 😸 (aka HomeyKit 3.0)

**URL:** <https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824>\
**Category:** Apps\
**Tags:** app, tools, devices, homey-pro\
**Created:** [November 29, 2022, 1:25pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824 "2022-11-29T13:25:03Z")\
**Posts on this page:** 20\
**Page:** 21

<div class="post-metadata">

**Author:** ![JMDPC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jmdpc/32/121098_2.png) [@JMDPC](https://community.homey.app/u/JMDPC)\
**Post date:** [March 3, 2026, 7:42pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/408 "2026-03-03T19:42:44Z")

</div>

Will work on it tonight

---

<div class="post-metadata">

**Author:** ![JMDPC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jmdpc/32/121098_2.png) [@JMDPC](https://community.homey.app/u/JMDPC)\
**Post date:** [March 4, 2026, 1:24am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/409 "2026-03-04T01:24:51Z")

</div>

Done

---

<div class="post-metadata">

**Author:** ![Jeppe\_Ladefoged](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeppe_ladefoged/32/113852_2.png) [@Jeppe\_Ladefoged](https://community.homey.app/u/Jeppe_Ladefoged)\
**Post date:** [March 12, 2026, 12:37pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/411 "2026-03-12T12:37:21Z")

</div>

Hi. I noticed that several of my Homekitty integrated devices started showing the “No response” triangle in the Home app recently. I’m only seeing this on “sensor” type devices - e.g. all my Philips Hue Motion Sensors, Aqara FP300’s (via Zigbee) and Aqara Smoke Detectors.

All devices and their properties (temp, lux etc.) show no signs of issues in Homey, but in Apple Home lux, temp, smoke detector test button show as “Not responding”. Lux meter on the Hue Motion Sensors for example are reporting value changes so i might only be cosmetic.

Just wondering if anyone else has encountered this issue?

 ![SCR-20260312-lxkg](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/6/56ef663ee31920a4f214fa7951e7ce2abc0ed059.jpeg)

---

<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:** [March 12, 2026, 1:22pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/412 "2026-03-12T13:22:21Z")

</div>

> [@Jeppe\_Ladefoged](#):
>
> Just wondering if anyone else has encountered this issue?

Please read the first post of this thread.

---

<div class="post-metadata">

**Author:** ![Jeppe\_Ladefoged](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeppe_ladefoged/32/113852_2.png) [@Jeppe\_Ladefoged](https://community.homey.app/u/Jeppe_Ladefoged)\
**Post date:** [March 12, 2026, 2:25pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/413 "2026-03-12T14:25:35Z")

</div>

Added a 30 sec. startup delay in app and that seems to have fixed it. Thanks for the tip and for a great app 🙏.

---

<div class="post-metadata">

**Author:** ![PaulG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paulg/32/121456_2.png) [@PaulG](https://community.homey.app/u/PaulG)\
**Post date:** [April 21, 2026, 10:35am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/414 "2026-04-21T10:35:33Z")

</div>

Looks like Homey Pro 13.1.2 has broken homekitty.

---

<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:** [April 21, 2026, 10:37am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/415 "2026-04-21T10:37:23Z")

</div>

A lot of stuff breaks after firmware updates, usually fixed by pulling the plug for a couple of minutes.

---

<div class="post-metadata">

**Author:** ![PaulG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paulg/32/121456_2.png) [@PaulG](https://community.homey.app/u/PaulG)\
**Post date:** [April 21, 2026, 10:47am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/416 "2026-04-21T10:47:04Z")

</div>

Yep tried all that…

---

<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:** [April 21, 2026, 10:54am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/417 "2026-04-21T10:54:26Z")

</div>

It’s working for me:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/0/2091dc26c7ca013ebf4c2587289ebabae0a3fc1c.jpeg)

So what are your _exact_ issues?

---

<div class="post-metadata">

**Author:** ![PaulG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paulg/32/121456_2.png) [@PaulG](https://community.homey.app/u/PaulG)\
**Post date:** [April 21, 2026, 10:55am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/418 "2026-04-21T10:55:59Z")

</div>

Are you updated to 13.1.2

---

<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:** [April 21, 2026, 10:56am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/419 "2026-04-21T10:56:49Z")

</div>

Yes:  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/7/3788fefdf61469074ae954d270031869e0d8ed17.png)

---

<div class="post-metadata">

**Author:** ![PaulG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paulg/32/121456_2.png) [@PaulG](https://community.homey.app/u/PaulG)\
**Post date:** [April 21, 2026, 11:02am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/420 "2026-04-21T11:02:13Z")

</div>

Strange… I show all offline 2min after homey updated to 13.1.2 also Konnected APP also offline.  
I run two hubs both are doing the same thing..

---

<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:** [April 21, 2026, 11:05am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/421 "2026-04-21T11:05:40Z")

</div>

After a boot it will take some time (up to 10 or 15 minutes) for HomeKitty to start publishing devices, because it often takes time for other apps to fully start and configure their devices. It wouldn’t surprise me of the Konnected app does the same.

---

<div class="post-metadata">

**Author:** ![PaulG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paulg/32/121456_2.png) [@PaulG](https://community.homey.app/u/PaulG)\
**Post date:** [April 21, 2026, 11:09am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/422 "2026-04-21T11:09:11Z")

</div>

It’s been three hours since I rebooted everything.

---

<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:** [April 21, 2026, 11:10am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/423 "2026-04-21T11:10:46Z")

</div>

That should be enough time 😅

Not sure why it’s not working anymore. Does Homey have a fixed IP address?

---

<div class="post-metadata">

**Author:** ![PaulG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paulg/32/121456_2.png) [@PaulG](https://community.homey.app/u/PaulG)\
**Post date:** [April 21, 2026, 11:11am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/424 "2026-04-21T11:11:26Z")

</div>

Yes

---

<div class="post-metadata">

**Author:** ![Gabriel\_Pedrosa\_Mach](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gabriel_pedrosa_mach/32/176567_2.png) [@Gabriel\_Pedrosa\_Mach](https://community.homey.app/u/Gabriel_Pedrosa_Mach)\
**Post date:** [April 22, 2026, 3:21pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/425 "2026-04-22T15:21:47Z")

</div>

Hi @robertklep,

I’m running HomeKitty 2.5.4 (test channel) on a Homey Pro 2023 (firmware 13.1.2) and I have two issues to share. I’ve also opened GitHub issues for both.

* * *

**Issue 1 — LG ThinQ air conditioners: wrong state and missing modes in HomeKit**

I have LG AC units integrated via the community app [LG ThinQ (com.verbem.smartthinq)](https://homey.app/en-br/app/com.verbem.smartthinq/LG-Thinq/). The device is an **LG Voice Wi-Fi** (model S4NW12JA31A.EB2GAMZ). Everything works perfectly inside Homey — on/off, thermostat modes (auto, cool, fan, dry), fan speed, airflow direction, all good.

After exporting to HomeKit via HomeKitty, the devices show up and current temperature is read correctly, but:

- The AC is physically **off** , but the Home app shows it as **active/on**
- The mode selector only shows **“Off” and “Auto”** — all other modes (cool, fan, dry) are missing
- Selecting “Off” in the Home app has **no effect** on the device

My best guess is that HomeKitty is mapping all `thermostat_mode` values to `auto`, since HomeKit’s Thermostat service only natively understands `heat`, `cool`, `auto`, and `off`.

* * *

**Issue 2 — Tuya gas sensor TS0204 shown as incompatible**

I also have a Tuya Zigbee gas detector (TS0204 / `_TYZB01_0w3d5uw3`), AC-powered, running on a custom community driver ([com.gpm.homesuite](https://github.com/gpmachado/com.gpm.homesuite)). The device works fine in Homey but HomeKitty marks it as **incompatible**.

The driver exposes `alarm_gas` (boolean) as its primary capability. An Aqara smoke sensor using `alarm_smoke` exports correctly from the same instance, my question is: do I need to change something in my driver to make it compatible, or is `alarm_gas` simply not supported by HomeKitty yet?"  
I’ve also reported both issues on GitHub. Thanks

 ![Captura de Tela 2026-04-22 às 11.55.17](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/8/08166cddcb3023e7e2e58852c88f43caf861c32a.png)

 ![Captura de Tela 2026-04-22 às 07.39.43](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/f/5f8676ee716bed27432c52fd5330f33d869724ae.png)

 ![Captura de Tela 2026-04-22 às 11.58.18](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/4/04e795b28887e203ed3a69cb12415758552746c0.jpeg)

 ![Captura de Tela 2026-04-22 às 11.58.30](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/9/79faa3cfaf0d4e9ea12d0aa40736ce1d388cec84.jpeg)

 ![Captura de Tela 2026-04-22 às 11.59.15](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/2/42dec503414464f23463ca43aabeeae8185476ee.jpeg)

 ![Captura de Tela 2026-04-22 às 11.59.26](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/5/456746be08e8aad5a30a01b0b9dcdcc625229e0f.jpeg)

 ![Captura de Tela 2026-04-22 às 11.59.49](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/3/9386041a9fc71463b97c864dbf7fc5c5336b9342.png)

 ![Captura de Tela 2026-04-22 às 11.57.59](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/e/6effffc1a15eb5f34623df9e13cf8dd594e81018.jpeg)

* * *

---

<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:** [April 22, 2026, 3:41pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/426 "2026-04-22T15:41:16Z")

</div>

I already responded to both your issues on Github.

---

<div class="post-metadata">

**Author:** ![Caesar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caesar/32/88727_2.png) [@Caesar](https://community.homey.app/u/Caesar)\
**Post date:** [April 25, 2026, 10:10am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/427 "2026-04-25T10:10:52Z")

</div>

It might be the Apple Home update ( x.4). I solved it by deleting all matter keychains from my iphone. Got the hint from Gemini. Rebooted Homey after that and it worked.

---

<div class="post-metadata">

**Author:** ![alexjje](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alexjje/32/121981_2.png) [@alexjje](https://community.homey.app/u/alexjje)\
**Post date:** [April 28, 2026, 6:58pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/428 "2026-04-28T18:58:36Z")

</div>

Hi Robert, my devices are no longer showing up in HomeKit. I’ve created a report: 124cbc6a-a805-4e37-9615-232383e1cca4

[Previous page](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824.md?page=20)

[Next page](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824.md?page=22)
