-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
ACs show up as fans in HomeKit #81445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) homekit documentation |
Assuming you paired it before 2022.11.0, you’ll need to unpair and repair the bridge as you have an accessory on the same bridge that previously did not have a stable iid For more details see the breaking change for HomeKit in the release notes |
I removed the bridge from iOS Home and Home Assistant, created a new bridge in HA and re-added it to iOS Home and the ACs still show up as fans. FWIW, on downgrading to 2022.10.5, they immediately showed up as ACs. In the screenshot above, note that the fan appears over the climate controls, it used to be the other way around before. |
Thats concerning considering since we haven't changed the thermostat code since september I'm not sure whats going on. |
When did you create the original bridge? |
At least a year back. |
I'm thinking whats happening is the service linkage needs to be the other way, but since the iids were unstable before when fan support was added the linkage was never seen. The HomeKit docs don't specify which direction the linkage should be though so its a bit a guess work. I can't test a change though since I'm traveling. |
If you are in a position to test, apply the below patch, restart, unpair, and repair commit 82a17b851a1b31457b395754bf6c79ac58ce5135
Author: J. Nick Koston <nick@koston.org>
Date: Thu Nov 3 10:55:15 2022 +0100
switch linkage
diff --git a/homeassistant/components/homekit/type_thermostats.py b/homeassistant/components/homekit/type_thermostats.py
index a924548816..a8c7a53718 100644
--- a/homeassistant/components/homekit/type_thermostats.py
+++ b/homeassistant/components/homekit/type_thermostats.py
@@ -306,7 +306,7 @@ class Thermostat(HomeAccessory):
if attributes.get(ATTR_HVAC_ACTION) is not None:
self.fan_chars.append(CHAR_CURRENT_FAN_STATE)
serv_fan = self.add_preload_service(SERV_FANV2, self.fan_chars)
- serv_thermostat.add_linked_service(serv_fan)
+ serv_fan.add_linked_service(serv_thermostat)
self.char_active = serv_fan.configure_char(
CHAR_ACTIVE, value=1, setter_callback=self._set_fan_active
)
|
That patch fixes the issue, can confirm, thanks. |
However, the fan continues to show above the climate controls. |
You might need to restart the device and all the home hubs as well (or wait a few hours) |
I have the same problem on version 2022.11.0. When I update to 2022.11.1, I unpair, repair the ACs, some of them still show up as fans. |
@lixplus0 Please post diagnostics |
Thanks but where could I find the diagnostics? It seems homeassistant did not report any error. |
You can find it on the integrations screen by clicking the tree dots next to the integration |
In this condition, five ACs were under this bridge. one was identified as AC, the other four were identified as Fans. config_entry-homekit-4a097c1e80cf4bf74f206e883b60abeb.json.txt |
Thanks. I see the problem. Working on a fix |
I had the same issue, but I found you can change the position of the fan controls in the home app - by tapping near the climate controls, and then closing and re-opening the accessory. In the end, I resorted to unlinking the tiles. |
Please try 2022.11.2 |
Thanks, 2022.11.2 fixed the issue. |
Uh oh!
There was an error while loading. Please reload this page.
The problem
Since 2022.11.0, ACs have been showing up as fans in the Home app.
What version of Home Assistant Core has the issue?
core-2022.11.0
What was the last working version of Home Assistant Core?
2022.10.5
What type of installation are you running?
Home Assistant Container
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: