HaBridge not discoverable by Alexa again #972
Comments
|
Since yesterday having serious trouble again with my Alexas and HA Bridge 5.2.0 on Rpi2, although local config untouched and unchanged. I think they (Amazon) are messing around again. I insist on saying "messing around" above and not "changing" or "updating", as it has been happening once every 2-3 month that Alexa stops working completely without any local changes - and this is really annoying me! |
|
How are you Pis connected to your router wi-fi or ethernet? |
|
Ethernet cable. Same as they’ve always been. Nothing has changed since the last time |
|
I've had issues with Alexa not seeing HA-Bridge configured devices. If you have Wi-fi possibilities enable it it worked for me. |
|
I’ll give that a go, but don’t really understand why that should make a difference when it’s always worked before |
|
I'm not sure if it is an Alexa thing or HA-Bridge thing as I use to have the same issue when running ha-bridge from my windows Desktop. Alexa would see the devices then periodically not, my desktop doesn't have Wi-Fi. |
|
I just installed the ha-bridge two days ago. I use a pi3 with WiFi and the same Pi for Alexa. Any idea? The WiFi does not seem to be the solution. |
|
I had no joy by enabling and switching to WiFi instead.....really puzzling for me....such a shame its been broken somewhere along the lines (it would seem) by Amazon. Hopefully it is fixed soon |
|
Today again, Alexa has Problems finding my HA Bridge. |
|
I can’t imagine it’s an issue with WiFi or lan as it’s always worked from day one on LAN without fail. As nothing has changed on my Pi, this HAS to be a change at Amazon’s end. Highly suggest no one removes any devices from Alexa for the foreseeable future until it can be confirmed this has been fixed in some way |
|
I'll try it again on my pi Zero wireless later on if I find some time. I now discovered that Amazon seems to have changed something recognizing German Special characters. These changes without noticing us users are terrible! |
|
None of my devices have any special characters in them. Tried renaming one but issue still |
|
Just to keep the thread updated.....still no change in discovery on Habridge from Alexa end. All other Alexa functions wor without issue and commands executed from directly within the HABridge UI work fine... |
|
still no change...really hope Amazon changes whatever they fixed/broke back again soon |
|
Hey jouster... Check out my post: Maybe try the old bridge (see reference in my post) by putting 1 item in it and see if it discovers? Maybe you and I have the same problem... Please note...IF you are going to try to modify the port from 8080 (i.e. you have OpenHAB like I do) and must change the ports, you may be better with 0.2.1. See my post here: To quickly get you going, download and run the jar(watch the parameters), then visit: It would be interesting if that works. But I don't know where to go from there, because I want to get away from that old code. *edit-fixed links |
|
a good few of your links were dead....I had already tried installing an earlier version on a separate SD card without success. As said, these devices were all working fine until I deleted all and try to rescan...in turn to find no devices....I'm still sure this has to be something at Amazons end |
|
actually, this is not the same project I referred you to, but it's what this project was forked from. I fixed all the links now. |
|
Just an update from my side: |
|
Still not able to detect anything on the system I have tried a completely fresh install all with the same results.. |
|
Add me as well to someone that can't connect their ha-bridge. I have an echo show |
|
Please post logs with traceupnp turned on and list the IP's of your ha-bridge host and your echo. Thanks |
|
Any update on providing logs? |
|
just doing now...apols been away for a few days |
|
My HABridge is running on my Rpi... IP Address is 10.107.8.55 running on port 82 The Echo I am running discovery from is 10.107.8.60 if you need any more info, please let me know
|
|
I do not see that address requesting anything, but you do see .41, .33 and .67 ask for upnp. What are those IPs related too? What is your network mask? Are you running in docker? |
|
67 is a Gen 2 Echo...41 is a NAS and 33 is my Harmony Hub Really strange as nothing has been changed in all the time its been set up so should be working as per usual. Standard setup on a rPi running full Stretch...nothing else running on it |
|
What is your network setup for the 10.107.8 network? netmask? |
|
not sure what you mean by how is it setup...nothing special really...subnet is just the standard 255.255.255.0 As said, nothing has been changed on either my network or my rPi and things just stopped working. |
|
Do you have a real philips hue? Does your Gen 2 Echo find the devices? Do you happen to connect the Harmony Hub to your ha-bridge to control things? |
|
INo I don't own any Hue devices...never have.... No devices find Habridge at all. I've tried it on my Dots, Show, Spot and Echo v2 and still hasn't worked Appreciate your time |
|
was there a recent update to raspbian os? Sometimes that messes with the networking. The only suggestion I have is to start looking at network dumps using tcpdump on the pi. |
|
Id love to say there has been but nothing has changed. That's what is so strange to me. I may just leave things a bit longer or do another complete rebuild without Stretch doing any updates and see if it that makes any difference again. It's incredibly frustrating for me and even more so for yourselves I am sure |
|
You may want to shut down all of your network gear, pi's and echos and then start them up in order... router, pi, echo... As this software and the pi are tinkerers items as they are not commercial nor built or supported that way. |
|
I totally understand that and have already done a full shutdown but will give it a go in the order you specify. I also appreciate that a Pi is very much a tinkering device and that things can and do break... |
|
@jouster1974 do you have your IPs reserved in your router? |
|
Since the latest Alexa roll out my HA-bridge devices are also not being seen :( |
|
Hi, I have the same issue. I can't find any device, please help me. |
I found the problem, the firewall was active and was blocking port 1900/udp |
|
I have an update on my side - I replaced the router on my location 2 that couldnt discover this bridge but could discover the old habridge, and now it works. I thought I had DD-WRT running on both, so it doesn't make sense to me - I'm sure if I did I had them configed the same. Anyway, working now! HOWEVER- sometimes Alexa gives a negative response - i.e. "xx not responding", but then it works anyway! I've added a couple 3rd gen devices if that matters. Maybe it's not getting a 2xx response back in time? Any idea how to troubleshoot-I'm not sure where to start with that one? |
|
I have HABridge 5.2.1 running on a Raspberry Pi Zero W (via WiFi). For 1-2 weeks now, I noticed that "xx not responding" AGAIN - although the command is executed correctly on my house automation system (FHEM). |
|
heikoh81 - I'm using that on PI Zero too. I'm wondering if it's a latency problem. Between the wifi and the slower speed of it, maybe it's a possibility. How taxed is yours? Does it run anything else? |
|
Sorry for the delayed reply. |
|
I am running ha-bridge on pi 3 and alexa app is not discovering it. I do not have a alexa hub though. Is alexa hub/echo required for ha-bridge or can it work with just alexa app ? |
|
You commented on a closed issue from May, BUT from the 3rd paragraph of the README
Please read the README. |
This could be just a blip on Amazon's side but thought I'd mention it all the same.
Needed to delete all devices on Alexa and when trying to rediscover it finds everything other than my HABridge devices.
Nothing has been changed at all on my rPi3 and it was all working fine before I had to delete all devices from Alexa. All devices on the bridge can be tested/controlled from HABridge...they just can't be discovered with Alexa I've tried using my Echo Dots, Echo Show, Alexa app on phone, and Alexa webpage...all with exactly the same results
This did happen back at the end of March and was affecting everyone so I'm really wondering if this is affecting everyone and if I should just take a look again in a few days.
Otherwise, is it possible that Amazon has updated something which has knocked out HABridge control for now?
TIA
The text was updated successfully, but these errors were encountered: