-
-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
Insignia Homekit Garage Door Opener #107137
Comments
Hey there @Jc2k, @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_controller documentation |
Anything in the logs? |
I can tell it is mentioned in the log but I can not tell what it is saying. I've attached the downloaded log. |
There are 2 devices that return a 404, can you double check they are operational? |
That would be the two "covers" (garage door openers, IP 192.168.1.165 and .166). The are powered up and operating correctly under core-2023.12.4. They only become disconnected when I upgrade to core 2024.1.0. I've gone through the upgrade then downgrade three times just to make sure. |
The homekit protocol doesn't return normally return 404 and HTML when a connection fails. Thats off spec and not very helpful of it. It looks like you have some homekit bluetooth devices. But do you have any other homekit ip devices? |
And when you downgrade, do you power cycle the garage openers or do they just start working? |
Looks like you have an ecobee that is working fine? |
Yeah Ecobee is fine and two Belkin mini's (switches), which are IP devices are working fine. The garage openers just start working without a restart when I downgrade. I did try a power cycle after the upgrade to see if that would get them working but it didn't. I did not try deleting them and trying to re-integrate them after the upgrade. These Insignia's can be difficult to get into HA at first. Once they integrate they seem to be pretty solid though. |
I noticed in the log the line, "Connecting to accessory failed: M2: Missing public key;" for both openers. I'm not sure of the mechanism for exchanging those keys but it must be done behind the scenes? I've never configured that anywhere before. |
Yeah when we connect we do the key exchange. We send an M1, then they send us an M2, then we send an M3 and they send an M4 and we are done. It's saying the M2 is invalid because it doesn't contain a key and aborting. That's correct because their M2 is a 404 and error html. |
The same log output for the previous version might be helpful, the most obvious explanation is that something changed in our headers. The host header was potentially changed as part of adding happy eyeballs. But it looks valid to my eyes. So comparison might be useful. |
Here is the core log for core-2023.12.4 but it doesn't look like there is anything in there relevant (I guess I should let you make that determination. I'm not so good with logs). |
It looks like debug logs aren't switched on, |
oops, sorry. Try this one. |
This is what I wanted to compare:
Vs
First one is the old code. 2nd is new. To my eyes things are choking because we put the port in the host header and didn't used to. |
related issue home-assistant/core#107137 When we added happy eyeballs, I added the port, but this seems to cause problems for some devices
Thanks! |
Let's see if our hunch is right first! Let us know how it goes when you get the next update :/ |
Will do.
…________________________________
From: Jc2k ***@***.***>
Sent: Thursday, January 4, 2024 1:43 PM
To: home-assistant/core ***@***.***>
Cc: Jaime Hall ***@***.***>; Author ***@***.***>
Subject: Re: [home-assistant/core] Insignia Homekit Garage Door Opener (Issue #107137)
Let's see if our hunch is right first! Let us know how it goes when you get the next update :/
—
Reply to this email directly, view it on GitHub<#107137 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AITSORBWHI2DO6X3AQ7POF3YM4PBXAVCNFSM6AAAAABBNDNRPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXHAYDAOBUGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I performed the latest update and it did not negatively affect my garage door openers. Thanks again!
…Sent from my iPad
On Jan 4, 2024, at 1:43 PM, Jc2k ***@***.***> wrote:
Let's see if our hunch is right first! Let us know how it goes when you get the next update :/
—
Reply to this email directly, view it on GitHub<#107137 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AITSORBWHI2DO6X3AQ7POF3YM4PBXAVCNFSM6AAAAABBNDNRPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXHAYDAOBUGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
home-assistant_2024-01-04T15-38-18.273Z.log
The problem
The Core update 2024.1.0 broke my Insignia Homekit Garage Door Opener. Rolling back to version 2023.12.4 fixed the issue.
What version of Home Assistant Core has the issue?
core-2024.1.0
What was the last working version of Home Assistant Core?
core-2023.12.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Homekit Device
Link to integration documentation on our website
https://www.home-assistant.io/integrations/homekit_controller/
Diagnostics information
Log attached.
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: