core: Problem with pairing Yeelight lightstrip with homekit controller on v2022.3.1
The problem
I am trying to pair yeelight lightstrip with homekit_controller.
First i paired it with Home app, then removed it and tried adding it via homekit_controller, then i get error
Cannot add pairing as device can no longer be found.
I even tried deleting homekit.state file but that only reseted my homekit bridge integration
I turned on debug logs for these but nothing showing there:
homeassistant.components.homekit_controller: debug
aiohomekit: debug
What version of Home Assistant Core has the issue?
2022.3.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Homekit Controller
Link to integration documentation on our website
https://www.home-assistant.io/integrations/homekit_controller/
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
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (6 by maintainers)
Commits related to this issue
- Bump aiohomekit to 0.7.17 Changelog: https://github.com/Jc2k/aiohomekit/compare/0.7.16...0.7.17 Fixes: #67665 — committed to bdraco/home-assistant by bdraco 2 years ago
- Bump aiohomekit to 0.7.17 Changelog: https://github.com/Jc2k/aiohomekit/compare/0.7.16...0.7.17 Fixes: #67665 — committed to bdraco/home-assistant by bdraco 2 years ago
- Bump aiohomekit to 0.7.17 (#70313) Changelog: https://github.com/Jc2k/aiohomekit/compare/0.7.16...0.7.17 Fixes: #67665 — committed to home-assistant/core by bdraco 2 years ago
- Bump aiohomekit to 0.7.17 (#70313) Changelog: https://github.com/Jc2k/aiohomekit/compare/0.7.16...0.7.17 Fixes: #67665 — committed to home-assistant/core by bdraco 2 years ago
Thank you man, this fixed it for me aswell.
I’m getting the same error on 2022.4.5. Adding a few debugs to the config flow gives:
Note that we’re looking in the cache for a lowercase device ID while zeroconf
properties.id
has uppercase.