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.

Sign up for GitHub

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

Jump to bottom

Ha Bridge 4.5.6 not detected by Alexa App, Show or on http://alexa.amazon.com #681

Closed
umarally opened this issue Jun 29, 2017 · 37 comments
Closed

Ha Bridge 4.5.6 not detected by Alexa App, Show or on http://alexa.amazon.com #681

umarally opened this issue Jun 29, 2017 · 37 comments
Labels
question

Comments

@umarally
Copy link

HI,

I have been trying to detect the Ha bridge (Which is detected by Hue App on my IOS) using Alexa but it doesn't discover the devices. I have tried it on multiple ports like 80,8080 etc. I have tried reinstalling raspbian on RPI3 multiple times and doing the setup again. I am able to access Ha bridge and control through : from any other device on my network but Alexa always gives me the same result, No device found
@masterchop
Copy link

i had the same problem, i had to rollback to 3.5.x after that everything worked fine again.

@umarally
Copy link
Author

I have already tried 3.5.1 and still didn't work for me

@bwssytems
Copy link
Owner

You will need to turn some debug on, please review this trouble shooting item and post your log afterwords https://github.com/bwssytems/ha-bridge/wiki/Trouble-Shooting#q-echo-or-google-home-does-not-discover-my-ha-bridge

@audiofreak9
Copy link
Collaborator

Just want to make sure you have a physical Echo, Dot or Tap, not just the app?

@umarally
Copy link
Author

I have the Echo Show - the new echo with a screen which I am using to discover the device. I will get the logs soon.

@bwssytems
Copy link
Owner

I'll need to you to turn in that Trace up listed in the link above. They may have changed something in the show.

@umarally
Copy link
Author

umarally commented Jul 1, 2017

Here, Also is there a basic requirement that detection has to be through a physical device? I have tried all three Echo Show, Alexa app and Web
UPNP logs.docx

@rafale77
Copy link

rafale77 commented Jul 2, 2017

Maybe this could help someone here. I just tried migrating from 3.5.1 to 4.5.6 and wanted to start from scratch as somehow Alexa has been very slow to respond to any hue command as I have been accumulating a lot of redundant devices (double discovered after an upgrade). I also tried moving my bridge from one VM to another and encountered this:

On the new VM, neither 3.5.1 nor 4.5.6 would discover the devices properly. When discovering from the Echo, it would sound like the devices were discovered as the number of devices in the response is correct (ie 59) but when I go into the echo app I see only 12 (all my non bridge devices). I went back to my old VM and did the same thing but all devices discovered properly. The only difference I can see between the 2 VMs is the network setup was missing the Broadcast address under /etc/network/interfaces (I am on ubuntu)

@bwssytems
Copy link
Owner

@umarally What devices did you add to your system? The logs show there are no devices configured. That is not the same as having systems configured in the bridge control tab.

@bwssytems
Copy link
Owner

@shannonmcmurtrey What is your specific issue? Your log shows something communicating with the ha-bridge.

@umarally
Copy link
Author

umarally commented Jul 6, 2017

i added some rf switches like Eteckcity ones. I can control those from the ha-bridge page.

@bwssytems
Copy link
Owner

@umarally What is the IP address of your Amazon Show?

@bwssytems
Copy link
Owner

@shannonmcmurtrey Which Alexa device do you have? And what is it's IP address?

@umarally
Copy link
Author

umarally commented Jul 6, 2017

192.168.1.20

@bwssytems
Copy link
Owner

@umarally Bad news for you, it looks like they did not implement the local hue api search for the Show. There are never any upnp requests in your log for that IP. You may have to buy an echo dot to get that functionality.

@bwssytems
Copy link
Owner

@shannonmcmurtrey You'll need to investigate the bridge control tab settings for upnp config address and that your network is allowing the upnp requests to flow from the wifi devices.

@umarally
Copy link
Author

umarally commented Jul 7, 2017

HI @bwssytems on the description page for Echo Show it says "Ask Alexa to show you the front door or monitor the baby's room with compatible cameras from Ring and Arlo. Turn on lights, control thermostats and more with WeMo, Philips Hue, ecobee, and other compatible smart home devices."

Since Philips Hue is mentioned and I thought the Ha Bridge mimicks a hue Bridge so it should be discovered. Just trying all the options that could resolve this.

@bwssytems
Copy link
Owner

@umarally Then there must be something preventing your show from sending upnp broadcasts as the request does not show up in your log for that ip.

@umarally
Copy link
Author

umarally commented Jul 7, 2017

yes, I noticed that as well. I have unblocked UNPN request on my router. Any other ideas where I can look to unblock this ?

@bwssytems
Copy link
Owner

I have no other ideas without seeing your whole network setup. Any news on this

@umarally
Copy link
Author

umarally commented Aug 1, 2017

so I bought a Echo Dot and it worked perfectly with that. Thanks I am closing this.

@umarally umarally closed this as completed Aug 1, 2017
@bwssytems
Copy link
Owner

That is unfortunate then. The Show must not do the discovery....

@masterchop
Copy link

3.5.1 works fine for me but 4,5.6 is not been detected this is so weird.

@willypowwow
Copy link

I had an issue with devices not being discovered. In my case, changing the Upnp address from localhost to the specific IP resolved the issue.

@heffneil
Copy link

I have upgraded to 5.0 and I can't find devices. I removed all my devices and added just one for this test. I know uPNP works because all my ip cameras are detectable. I am trying with the website and a show. I will try with an dot next. Its very odd. The upnp address is the IP of the machine so that is confirmed as well. Any other ideas?

@bwssytems
Copy link
Owner

Are you also using web port 80, it is default unless overridden.

@heffneil
Copy link

Yes I am using port 80. I believe I was using port 80 prior but I could be wrong. Is there a way to change ports for the UPNP? I noticed the response port is set to 5000. Thanks!

@umarally
Copy link
Author

try with a echo dot. Echo show was not detecting my devices over UNPN

@heffneil
Copy link

How does one override the UPNP port?

@heffneil
Copy link

I changed the port on Apache to 80 and it doesn't work - this is with an echo show. I will try when I go upstairs on a dot. Seems odd that one would work vs another?!

@heffneil
Copy link

I tried with an echo dot, didn't work. I tried with two different Shows. I was concerned about being in different subnets although my subnet is set to 255.255.0.0 in DHCP. I setup a reservation in the DHCP server so I confirmed that this Echo Show and my server are all in the same class C of 192.168.1.x

@michaelhinchey
Copy link

michaelhinchey commented Nov 28, 2017 via email

@heffneil
Copy link

heffneil commented Nov 28, 2017 via email

@heffneil
Copy link

heffneil commented Dec 1, 2017

So today I tried it again just now. I did the search from the Alexa website and it found them! BTW i do run apache and have always run apache on port 80 and it has never been a problem. I have NO idea why it works today because the other day I had tried from the website and it didn't find them. Very very strange but for today its working!

@sheriffdude
Copy link

hi guy how do you run ha bridge on port 80 mine is se to run or start with a batch file
ie java -jar -Dserver.port=8081 ha-bridge.jar this starts my ha bridge ..then i use http://localhost:8081/#!/ to show bridge ..i can turn my easy bulbs of and on but can not get my echo dot to find the ha bridge if i change web server port to 80 and save it just goes back to 8081

@mikep809
Copy link

Everything was working fine until i migrated to 5.2? Now none of my x10 devices are found with my dots. Any ideas?

@echery
Copy link

echery commented Jul 28, 2018

Make sure ha-bridge is using the same UPNP address as the one used to access it from the browser. My setup didn't originally because the UPNP auto discovered a random IP that was not the IP for ha-bridge.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests