Will work on it tonight
Done
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?
Please read the first post of this thread.
Added a 30 sec. startup delay in app and that seems to have fixed it. Thanks for the tip and for a great app
.
Looks like Homey Pro 13.1.2 has broken homekitty.
A lot of stuff breaks after firmware updates, usually fixed by pulling the plug for a couple of minutes.
Yep tried all that…
Are you updated to 13.1.2
Yes:

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..
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.
It’s been three hours since I rebooted everything.
That should be enough time ![]()
Not sure why it’s not working anymore. Does Homey have a fixed IP address?
Yes
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). 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). 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
I already responded to both your issues on Github.
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.
Hi Robert, my devices are no longer showing up in HomeKit. I’ve created a report: 124cbc6a-a805-4e37-9615-232383e1cca4









