Skip to content
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

Onvis HS2 unable to be added to Home Assistant / Thread / Homekit #135025

Open
pdobrien3 opened this issue Jan 7, 2025 · 1 comment
Open

Onvis HS2 unable to be added to Home Assistant / Thread / Homekit #135025

pdobrien3 opened this issue Jan 7, 2025 · 1 comment

Comments

@pdobrien3
Copy link

The problem

The Onvis HS2 is a homekit/thread button. I have two of them. The first one I purchased a while ago and was easily able to add it to Home Assistant by first adding it to Apple Home, removing it, and adding it as a homekit device in Home Assistant. I liked the first one so much, I recently purchased a second but I have been unable to add it to Home Assistant. There are several posts on the forum of people with similar issues. What I have tried:

  1. Adding with Apple Home to get thread credential, removing from apple home and adding to HAss. Immediately upon removing from Apple Home, the device pops up as discovered in HAss. When you try add it, I always get the same error: This accessory is already paired to another device. Please reset the accessory and try again.
  2. Adding to the Onvis app to get thread credentials, removing from the onvis app, and adding to Home Assistant. This process results in the same error as step 1 above
  3. Setting up a bluetooth proxy to add the device via bluetooth. The device is always discovered, but when attempting to add I get errors related to the inability to conect, tried 9/10 times, as well as the following error during the onboarding process:
    Config flow could not be loaded: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->

What version of Home Assistant Core has the issue?

2025.1.0

What was the last working version of Home Assistant Core?

unknown when i initially added the first device

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Thread

Link to integration documentation on our website

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

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

@home-assistant
Copy link

home-assistant bot commented Jan 7, 2025

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (thread) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of thread can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign thread Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


thread documentation
thread source
(message by IssueLinks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant