core: Devices are becoming unavailable every 1-3 minutes

The problem

After upgrading to core-2021.7.0 today, all of my climate devices become ‘Unavailable’ every 1-3 minutes, and then return to working order again. This process has been repeating constantly since the core update.

The devices are using Homebridge and the Frigidaire plugin in a local docker container. I have 2 other similar Homebridge containers but those devices (Harmony plugin and Cmd4 plugin) are not experiencing these issues in HA.

These climate devices were working fine prior to today’s HA Core update. I have already rebooted the host and restarted HA multiple times.

What is version of Home Assistant Core has the issue?

core-2021.7.0

What was the last working version of Home Assistant Core?

core-2021.6.6

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Homekit Controller

Link to integration documentation on our website

https://www.home-assistant.io/integrations/homekit_controller/

Example YAML snippet

N/A

Anything in the logs that might be useful for us?

2021-07-07 18:26:37 DEBUG (MainThread) [homeassistant.components.homekit_controller.connection] Starting HomeKit controller update: 0E:32:23:EF:2A:21
2021-07-07 18:26:37 DEBUG (MainThread) [aiohomekit.controller.ip.connection] 192.168.86.36: raw request: b'GET /characteristics?id=2.10,2.11,2.12,2.13,3.10,3.11,3.12,3.13,4.10,4.11,4.12,4.13,2.12,3.12,4.12 HTTP/1.1\r\nHost: 192.168.86.36\r\n\r\n'
2021-07-07 18:26:37 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Got HTTP error 422 for GET against /characteristics?id=2.10,2.11,2.12,2.13,3.10,3.11,3.12,3.13,4.10,4.11,4.12,4.13,2.12,3.12,4.12
2021-07-07 18:26:37 DEBUG (MainThread) [homeassistant.components.homekit_controller.connection] Called async_set_available_state with False for 0E:32:23:EF:2A:21
2021-07-07 18:26:37 DEBUG (MainThread) [aiohomekit.controller.ip.connection] 192.168.86.48: raw response: bytearray(b'{"characteristics":[{"aid":1,"iid":18,"value":false},{"aid":1,"iid":19,"value":true},{"aid":1,"iid":31,"value":false},{"aid":1,"iid":20,"value":100}]}')

Additional information

Portainer-based Homebridge container (Docker)
Hombridge Frigidaire plugin for AC climate devices

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 21 (12 by maintainers)

Commits related to this issue

Workaround for https://github.com/home-assistant/core/issues/52680 — committed to Jc2k/aiohomekit by Jc2k 3 years ago
Merge pull request #45 from Jc2k/homekit_controller_52680 Workaround for https://github.com/home-assistant/core/issues/52680 — committed to Jc2k/aiohomekit by Jc2k 3 years ago

Most upvoted comments

I’m actually super excited to learn about that homebridge plugin, I backed the Switch Bot Curtains kickstarter and have some waiting in a box for when I have some free time!

There’s not much we can check without you upgrading and testing a 1-line fix for me unfortunately!

Jc2k on Jul 8, 2021

@gvssr your case is odd, so thanks for bringing it up. The other 2 cases are where a climate device gets a climate entity and a temperature sensor as a seperate sensor, which is expected now. But in your case I can’t see why you would legitimately have a duplicate characteristic tuple getting set to the device. So I think you are hitting the same homebridge specific bug, but are hitting it because of a 2nd bug. I’m guessing it’s because of the annyoing vendor specific thing where some accessories return full UUID’s and some return short hand UUID for Apple charactersitics and services. Assuming I didn’t normalise one properly somewhere. Will see what I can see…

Jc2k on Jul 8, 2021

@amaisano brilliant as above:

GET /characteristics?id=2.10,2.11,2.12,2.13,3.10,3.11,3.12,3.13,4.10,4.11,4.12,4.13,2.12,3.12,4.12

Contains a duplicate 2.12, which homebridge seems to not like. My fix in https://github.com/Jc2k/aiohomekit/pull/45 should sort that out.

Jc2k on Jul 8, 2021