# \[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:** 11

<div class="post-metadata">

**Author:** ![Damian](https://avatars.discourse-cdn.com/v4/letter/d/34f0e0/32.png) [@Damian](https://community.homey.app/u/Damian)\
**Post date:** [February 14, 2024, 6:23pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/204 "2024-02-14T18:23:14Z")

</div>

Hi, have you thought about adding wider support for Xiaomi air purifiers? Currently it works on an on-off basis, maybe it would be possible to add speed regulation?

The second device is adding an iRobot vacuum cleaner to Apple Home 🙂

---

<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:** [February 15, 2024, 6:16am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/205 "2024-02-15T06:16:54Z")

</div>

> [@Damian](#):
>
> Hi, have you thought about adding wider support for Xiaomi air purifiers?

No, that’s not something I think about 🤷🏼‍♂️

> [@](#):
>
> Currently it works on an on-off basis, maybe it would be possible to add speed regulation?  
> The second device is adding an iRobot vacuum cleaner to Apple Home 🙂

If you want specific device support, please [create a separate issue for each device on Github](https://github.com/robertklep/name.klep.homekitty/issues/new?assignees=&labels=&projects=&template=feature-request-unsupported-device.md&title=%5BFeature+Request%2FUnsupported%5D). The issue template will ask for information that I need to know before I can say if adding support is possible.

---

<div class="post-metadata">

**Author:** ![BGSmith](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bgsmith/32/80328_2.png) [@BGSmith](https://community.homey.app/u/BGSmith)\
**Post date:** [March 10, 2024, 6:24am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/206 "2024-03-10T06:24:06Z")

</div>

Hi there - before I post to GitHub, I wanted to check to see if this is a known problem.

I love the application, thank you for all your work in developing and supporting it.

I have a Nest thermostat which works, arguably , correctly through the Homey app with my Homey Pro. However, when i setup HomeKitty, the temperature is wildly off (68° F in Nest or Homey, 158° F in Home).

Is this a known issue? If not, I’ll open a ticket. I didn’t want to do that if it’s something everyone already knows about (since, I don’t have a Starling, I’m guessing this might be a pipe dream anyhow)

Thanks again!

Brian

---

<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 10, 2024, 6:47am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/207 "2024-03-10T06:47:24Z")

</div>

> [@BGSmith](#):
>
> However, when i setup HomeKitty, the temperature is wildly off (68° F in Nest or Homey, 158° F in Home).

Internally, Homey always works with Celsius so HomeKitty sets the “temperature display units” to Celcius as well. My guess is that there’s still a conversion going on somewhere (although 158F is not 68C, which is strange), but I’m not sure where.

Can you find your device [here](https://tools.developer.homey.app/tools/devices) and check the values of the measured and target temperatures?

**EDIT** : I now see that HomeKitty might not be setting the temperature units correctly. I’ll try and see if I can fix that.

**EDIT 2** : try the latest test version (v2.2.13): [HomeKitty | Homey](https://homey.app/a/name.klep.homekitty/test/)

---

<div class="post-metadata">

**Author:** ![BGSmith](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bgsmith/32/80328_2.png) [@BGSmith](https://community.homey.app/u/BGSmith)\
**Post date:** [March 10, 2024, 2:51pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/208 "2024-03-10T14:51:40Z")

</div>

Thanks for looking into this. Here’s the update. I installed the 2.2.13 version, and didn’t see a change immediately.

- I restarted the HomeKitty app, and went to app settings and toggled the Thermostat from devices list. Saw it disappear from Home, and toggled it back on. Same error.

- I went to the Nest app, and did a “attempt to repair” … no difference.

- So I removed the device from Nest and re-added it, et voila, we have a change, but a new error. It was reading 32° C in Home, while reading 68° F in Homey (in the time I’ve been writing this, it’s gone back to 156°)

Another interesting thing is device status isn’t correct. In Homey it is on/Heat (current temp 68° / set point 71° and it’s runnng) where as in Home, it’s showing as Off, current temp 156°, humidity 0%, and set temp 50°)

 ![IMG_2850](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/4/a4a23850f3bd45f63f9d72fadd31114631ae746a.jpeg)  
 ![IMG_2851](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/2/02162325d3f00816109a1456dc554726bb8c5b8f.png)  
 ![IMG_2852](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/f/cf4c31e86979f2ef820ef50e3037292e7c09bc78.png)

---

<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 10, 2024, 3:24pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/209 "2024-03-10T15:24:19Z")

</div>

Both `measure_temperature` and `target_temperature` capabilities in Homey aren’t correct, they should contain the Celsius value but they contain the Fahrenheit value. That’s an issue with the Nest app, not something HomeKitty can fix.

Also, `nest_thermostat_mode` is a custom capability, unique to the Nest app, and HomeKitty doesn’t support those.

I’m not sure why the humidity isn’t shown correctly, though.

---

<div class="post-metadata">

**Author:** ![BGSmith](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bgsmith/32/80328_2.png) [@BGSmith](https://community.homey.app/u/BGSmith)\
**Post date:** [March 10, 2024, 8:52pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/210 "2024-03-10T20:52:07Z")

</div>

Oh, no, the `measure_temperature Temperaturenumber 69` and `target_temperature Heat number 71` in Homey are correct and match what’s in the native app, and on the device display (all in F). It is only the Home where the problem exists.

I’m trying some different formulas, and it’s possible that the calculation is trying the (9/5) multiplication against the F temperature, and then adding 32 to the result. I believe the correct order of operations is {(°F-32)\* (5/9)} to get to °C.

If I try (°F \* (9/5))+32 it gets to 155 which is what’s showing up in Home.

---

<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 11, 2024, 5:43am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/211 "2024-03-11T05:43:02Z")

</div>

> [@BGSmith](#):
>
> Oh, no, the `measure_temperature Temperaturenumber 69` and `target_temperature Heat number 71` in Homey are correct

I understand that you think they are correct, but they’re not: they should be in Celsius, because that’s what Homey uses internally. Only when temperatures are displayed (mobile app, web app) should they be converted to the local temperature scale.

This is the unit definition of `measure_temperature`:

```auto
  "units": {
    "en": "°C"
  },

```

This is an issue with the Nest app that I cannot fix.

> [@](#):
>
> If I try (°F \* (9/5))+32 it gets to 155 which is what’s showing up in Home.

What’s happening is that Home also assumes that the temperatures supplied by HomeKitty are in Celcius, and subsequently converts them to your local preference.

---

<div class="post-metadata">

**Author:** ![Valtsu](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/valtsu/32/70931_2.png) [@Valtsu](https://community.homey.app/u/Valtsu)\
**Post date:** [April 3, 2024, 5:02pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/214 "2024-04-03T17:02:02Z")

</div>

Had some major issues first with the HomeKit experiment and then with the HomeKitty. Both of them published the devices to HomeKit, but neither of them gave access to any of the devices. All devices remained “not responding” no matter what…until I removed all my 3 Apple TVs and two HomePod minis from the picture…scarabough and now it’s all working with HomeKitty!

Well almost all…for some reason my Aqara and Sonoff temperature sensors do not show up in HomeKit although they are toggled on in the HomeKitty’s list of devices. Any ideas how to get them working?

---

<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 3, 2024, 5:09pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/215 "2024-04-03T17:09:35Z")

</div>

> [@Valtsu](#):
>
> until I removed all my 3 Apple TVs and two HomePod minis from the picture…scarabough and now it’s all working with HomeKitty!

That’s fairly common, although usually a reboot of those devices will be enough.

> [@](#):
>
> Well almost all…for some reason my Aqara and Sonoff temperature sensors do not show up in HomeKit although they are toggled on in the HomeKitty’s list of devices. Any ideas how to get them working?

If they are toggled on it means they are supported by HomeKitty, and passed to iOS, but sensors aren’t shown as separate devices until you dig deeper, for instance through the Climate category and then clicking Temperature/Humidity.

---

<div class="post-metadata">

**Author:** ![Valtsu](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/valtsu/32/70931_2.png) [@Valtsu](https://community.homey.app/u/Valtsu)\
**Post date:** [April 3, 2024, 6:13pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/216 "2024-04-03T18:13:33Z")

</div>

> [@robertklep](#):
>
> aren’t shown as separate devices until you dig deeper

Ooh now I found them. However for some odd reason they only show humidity data and not temperature at all. I recall having the same issue with the Homey’s HomeKit experiment.

Edit: I take my words back. Both are shown.

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [April 21, 2024, 1:58pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/217 "2024-04-21T13:58:57Z")

</div>

Split this topic on April 21, 2024, 1:58pm UTC

A post was merged into an existing topic: [[App][Pro] HomeyKit](https://community.homey.app/t/app-pro-homeykit/70469/56)

---

<div class="post-metadata">

**Author:** ![xazac](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/xazac/32/132591_2.png) [@xazac](https://community.homey.app/u/xazac)\
**Post date:** [May 1, 2024, 10:06pm UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/218 "2024-05-01T22:06:34Z")

</div>

Hello,

Xiaomi Air Purifier 3H is not recognized as Air Purifier but like a simple switch with your plugin.

Can you please fix this?  
Thanks

---

<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:** [May 2, 2024, 4:29am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/219 "2024-05-02T04:29:29Z")

</div>

It’s likely nothing has changed [since this request for device support](https://github.com/robertklep/name.klep.homekitty/issues/89) so it’s probably not possible to add support for it.

---

<div class="post-metadata">

**Author:** ![xazac](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/xazac/32/132591_2.png) [@xazac](https://community.homey.app/u/xazac)\
**Post date:** [May 2, 2024, 10:14am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/220 "2024-05-02T10:14:41Z")

</div>

This works great: [GitHub - merdok/homebridge-miot: Homebridge plugin for devices supporting the Xiaomi miot protocol](https://github.com/merdok/homebridge-miot)

---

<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:** [May 2, 2024, 11:08am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/221 "2024-05-02T11:08:14Z")

</div>

Homey works in a completely different way.

---

<div class="post-metadata">

**Author:** ![jon0](https://avatars.discourse-cdn.com/v4/letter/j/ecccb3/32.png) [@jon0](https://community.homey.app/u/jon0)\
**Post date:** [May 9, 2024, 4:17am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/222 "2024-05-09T04:17:09Z")

</div>

This same issue occurs with the Honeywell Home app, unfortunately.

---

<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:** [May 9, 2024, 4:18am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/223 "2024-05-09T04:18:57Z")

</div>

It’s still not an issue with HomeKitty ☹

---

<div class="post-metadata">

**Author:** ![jon0](https://avatars.discourse-cdn.com/v4/letter/j/ecccb3/32.png) [@jon0](https://community.homey.app/u/jon0)\
**Post date:** [May 9, 2024, 6:23am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/224 "2024-05-09T06:23:54Z")

</div>

Ah sorry I meant “issue” as in problem, not issue with HomeKitty. I probably ought to file a report against the Athom app for this I’m guessing?

---

<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:** [May 9, 2024, 7:05am UTC](https://community.homey.app/t/app-pro-homekitty-aka-homeykit-3-0/72824/225 "2024-05-09T07:05:41Z")

</div>

Yes, it sounds as if the Honeywell Home app does the same as the Nest app: it doesn’t (or possibly isn’t even able to) check the temperature scale of the device, and it assumes the device provides temperatures in Celcius, even if the device uses Fahrenheit.

Athom should fix this in the Honeywell app.

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

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