-
Notifications
You must be signed in to change notification settings - Fork 199
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
HABridge not working anymore since today #1410
Comments
Devices are also not found anymore when removing them from and trying to readd them to the Alexa app. |
I had a mixture of <9 digits long UUIDs. Worked for years with HA Bridge 5.4.1. |
I was using HA Bridge a few years back and it worked great. About a week ago a new need surfaced so I tried to fire it up again. I was able to get the test buttons (on & off) working for a new device and had no issue. Then, I tried to get Alexa to discover devices, with no luck. I went through a bunch of the articles to make sure I had everything set up correctly. (Even a simple “how to” article, that I saved for back in 2019/2020). Nothing seems to work to get Alexa to discover the new device. I even upgraded to 5.4.1 from 5.2.2. Still no luck. Then I found this thread, and now I'm wondering if the issue is more with Alexa having an issue, then my configuration. Any, Help / Advice would be greatly appreciated. Also, I seem to recall back then that the My Echo button worked beyond bringing up a page to get to the Alexa app. Thanks in advance for any help. --- UPDATE --- Moved the HA Bridge Folder to another box and used Port 80. Discovery now works! ----- |
Alexa replies: "... reagiert leider nicht". HABridge does not respond to Alexa anymore :-(
Testing Buttons from HABridge WebUI are working.
The text was updated successfully, but these errors were encountered: