Ha-bridge: Echo Second Edition not discoverying HA bridge 5.0.0(synology)

[haymaan]

hallo,
i was enjoying the Habridge(4-5-6) synology ver in combi with Alexa DOT 2,and every thing works fine,,,,
after update to Echo Second Gen it's not detecting the HA bridge,i've update the bridge to 5-0-0,and still not working ,HA bridge working fine throught compuer/mobile.....

i have Synology and use poort 8088 for the bridge,that was not a probleem with Dot 2...please help

[michaelhinchey]

Try port 80

Every dream is a goal with a date on it; if you can conceive it believe

it, you can achieve it. Don't let anyone steal your dream. Make the
decision to take a positive attitude, take pride in yourself and what you
do, work hard and stay with it. A mind is a terrible thing to waste.

"I felt bad because I couldn't wheelie; until I met a man with no bicycle"

"You are young at any age... if you are planning on tomorrow"

On Nov 26, 2017 11:47 AM, "haymaan" [e-mail] wrote:

hallo,
i was enjoying the Habridge(4-5-6) synology ver in combi with Alexa DOT
2,and every thing works fine,,,,
after update to Echo Second Gen it's not detecting the HA bridge,i've
update the bridge to 5-0-0,and still not working ,HA bridge working fine
throught compuer/mobile.....

i have Synology and use poort 8088 for the bridge,that was not a probleem
with Dot 2...please help

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bwssytems/ha-bridge/issues/810, or mute the thread
https://github.com/notifications/unsubscribe-auth/AV9KHJqBZDcp-Pk-Cu7xyCGEZHiBHtd2ks5s6ZYSgaJpZM4Qq1mO
.

[haymaan]

thanks will try that ...

[bwssytems]

Did port 80 solve your issue?

[haymaan]

No still the same problem ,are there any other with this problem??

[varguello]

Exact same issue with my brand new Echo 2nd gen. Echo Dot works fine. Once Echo Dot has sent a successful request to the device my Echo 2nd gen seems to find it for a while but "forgets" it again. Habridge (5.0.0) is running on Synology DS214play on port 81.

[bwssytems]

So, I will need you to turn on trace upnp and do a discover with the 2nd gen Echo and post the entire log.

Thanks

[varguello]

Here it goes:
traceupnp.txt

[bwssytems]

I assume the 2nd gen echo is IP 192.168.5.171. It looks like it asks for the description.xml but does not use that information to go get the lights list. For fun, does the 2nd gen echo work with 4.5.6?

[haymaan]

No it's even not working with 4.5.6....
thanks

[varguello]

I can confirm it too. It doesn't work on 4.5.6. The trace is basically the same (aside from different formatting). The echo 2nd gen does not query the hue lights.
traceupnp-4.5.6.txt

[bwssytems]

Well, this is not good. So they changed some interpretation on querying info from the description.xml.

[haymaan]

thanks for the reply ,is there any way that can fixed ..?

[bwssytems]

It will take some research as this would be a reverse engineering endeavor.

[bwssytems]

Anyone with a 2nd gen Echo and a real philips hue that could do a trace on messages used during discover on the philips hue? There must be something in the update hue description.xml that is needed.

[chrismillsuk]

I have an echo plus and at first no devices found on auto discover from app or echo. But after doing a discover scenes on the app all my devices appear and work, the only other thing I’ve notice if I rename a device or add on I have to reboot echo to get it to notice changes.

[NorthernMan54]

@bwssytems I just started playing with this in my setup, and it appears to only respond to Hue Emulators on port 80. Have you tried that?

I'm dealing with a similar V2 issue, with the hue emulator I built into homebridge. https://github.com/NorthernMan54/homebridge-alexa/issues/32

[cw-kid]

I have been using an Echo DOT OK with HA-Bridge for sometime, recently I also added a gen 2 Echo.
I then later decided to buy several Google Home speakers instead (Also not working with HA-Bridge either) .

So I unregistered and removed the gen 2 Echo. However seems since then, that the original Echo Dot which I plan to keep, now no longer detects any devices from the HA-Bridge.

I was running HA-Bridge on port 8087 on my Windows server, I have just tried running it on port 80 instead but the Echo Dot is still not detecting devices.

I dare not press the Forget All devices button in case none of them come back.

Tried HA-Bridge 4.5.6 and just updated it to 5.0.0.

So has temporarily adding a gen 2 Echo device to my setup, now broken the original Echo Dot from being able to add devices from the HA-Bridge ?

Thanks

[cw-kid]

I have managed to get my Echo Dot to discover devices from HA-Bridge now. But seems I have to do things a bit differently than before though.

Previously I was using a gen 1 Hue bridge. Two days ago I migrated to a new gen 2 Hue bridge. It now seems I have to power off the real Hue bridge before discovering devices in the Alexa app.

Also now it seems you have to set the HA-Bridge to port 80 as well. As when the bridge is set to my regular port number it does not work and Alexa will not find any new devices.

Once Alexa had discovered the new devices off the HA-Bridge I then changed the port number back from 80 to my regular port number I use and then nothing works, I wasn't able to turn on or off any devices from the Alexa app.

So seems HA-Bridge now needs to be on port 80 all the time. I cannot do this on my Windows server as I have another service on port 80.

So time to run HA-Bridge on a Raspberry Pi or use something else instead of HA-Bridge.

Also since updating to HA-Bridge 5.0.0 I am seeing loads of these messages constantly.

"The requested route [/(null)] has not been mapped in Spark for Accept: [null]"

[cw-kid]

Can you specify which IP address HA-Bridge should run on ?

Thinking maybe I could add a second IP address to my Windows server and have HA-Bridge run on port 80 on that secondary IP address.

Thus allowing port 80 on the primary IP address to still be used for the webserver.

EDIT:

I have added a secondary IP address to the WHS server and I can ping that OK from my mac. I then changed the HA-Bridge startup batch file to specify it should now use this new IP address etc. I have Windows Firewall turned off on the server but when I try now to connect to HA-Bridge in the browser on the new ip address I get: ERR_CONNECTION_REFUSED

[bwssytems]

@cw-kid Make sure you didn't use the web server address feature in the ha-bridge, that would prevent it from binding to the correct interface. Also, it seems that Amazon has now updated the echo software across the board to only go to port 80 from what you have shown.

[cw-kid]

I kinda messed up my WHS 2011 server a bit today trying to get this working.

I added a secondary IP address and I changed the HA-Bridge to start up with this new IP and also that it should use Port 80.

In IIS for the Default Website aka the WHS 2011 remote access page, Port 80 was binded to All unassigned IP addresses. I changed this to only use the first IP address of the server.

I was then able to access HA-Bridge, on the new secondary IP address and on port 80.

However I was then unable to also access the WHS 2011 RWA page via the servers first IP address on port 80 / 443. The page wouldn't load.

So I couldn't seem to get both running on different IPs but both using port 80 etc.

I have currently set everything back to how it was before I started and rebooted the server. This has fixed the WHS 2011 RWA page but HA-Bridge still isn't working.

In fact now for some reason whatever port I specify for HA-Bridge it now never seems to stay running, it goes through the motions of starting up but then just vanishes and isn't running. So think I have really broken HA-Bridge now.

[cw-kid]

If I rename the data folder to data.old and create a new blank data folder HA bridge starts again now, so must have messed up my original data folder ?

I've managed to use one of the backup config files and it looks like I did have the "Web Server IP Address" and "Web Server Port" fields populated.

I should leave these blank I guess and just specify the IP and Port in my startup batch file.

EDIT: Actually blanking them out kills it. So these values are auto populated with what IP and Port I specify in my startup batch file?

[cw-kid]

I give up I cannot get HA bridge to run on port 80 on the WHS 2011 server and also have the server run its stuff on port 80 also, even with two IP addresses and messing about with bindings in IIS.

Now switching to Vera's native skill for Alexa instead as that wasn't available when I first setup HA-Bridge.

Thanks

EDIT: But still need HA Bridge for the Harmony Elite. But it doesn't matter if its not running on port 80 as it still works OK with the Harmony.

[haymaan]

why closed there is no way to get it works ... ?

[happyhammers]

Any closer to finding a fix, I've tried port 80 still no luck. I can not get my gen 2 echo to see bridge. Cheers Dave

[cw-kid]

Power off your real Hue bridge as well, I had to do that also before my Echo Dot / Alexa web app would discover devices from the HA-Bridge.

Can't comment on actual gen 2 Echo devices as haven't got one now.

[bwssytems]

@haymaan It's not closed, it is a reference to an other issue that was a duplicate that is closed

[NorthernMan54]

@bwssytems I have a Echo 2nd generation and the Hue V1 hub ( round ) and am still looking at this. So far I have found that my code gets stuck on the /api/username/light/# response. I'm sending the response, which is copied from my V1, but it m my echo just repeats the request. Tomorrow I'm going to confirm if my echo 2nd generation does work with my Hue V1. If that doesn't work then it may be a Amazon defect.

[avenantsoftware]

I just bought an echo dot version 2, and noticed that alexa doesn't discover the ha bridge, but when you ask alexa: discover devices, and then under 'bridge control" => "bridge reinitilize", if you do this when alexa is trying to discover your devices, then alexa finds it...

also once alexa has found everything, never hit the button "renumber devices" because then everything is screwed up, I found this out the hard way LOL

[haymaan]

i'll try it tonight thanks

[bwssytems]

Please try the new release 5.1.0 https://github.com/bwssytems/ha-bridge/releases/tag/v5.1.0

[smorks]

5.1.0 worked right away for me with my echo dot 2nd gen. thanks for the quick fix!

[Ordep]

Are you using a specific port? How are finding new devices? (Voice, app, web)
I have the echo 2nd gen, but didn't work. I'm might be doing something wrong though.

[cw-kid]

So do you still need to use port 80 with version 5.1.0 of HA bridge?

[cw-kid]

Appears to be working again now on ports other than 80. My HA Bridge is on port 8087 and I have updated the Bridge to version 5.1.0. In the Alexa web app I forgot all devices and re-discovered them. It has now added back in devices from the HA-Bridge !

[Ordep]

I'll try to use the webapp instead of the app and forget all devices before re-discover them.

Wasn't working for me this morning in any port, but probably was because I haven't removed all existent devices (non ha-bridge)

[Andi1927]

I tried it also with the Web app and port 8080 on a synology but doesn´t work with my 2.end Edition of Echo. Maybe I make something wrong.

[cw-kid]

I only have an Echo Dot not a gen 2 Echo. You might need to still use port 80 for that to work.

[michbeck100]

@cw-kid echo dot always worked. just test with the new Echo (2nd gen)

[cw-kid]

It wasnt working the other day unless Ha bridge was on port 80 and also the real hue bridge powered off.

[haymaan]

still not working even with 5.1.0 ,,
hope will it fix soon

[Andi1927]

For me it is working Echo and echo dot both 2nd gen. It works since 5.1.0.
Port 8080
So thanks for the good job

[haymaan]

Which device you use for HAbridge??

[Andi1927]

I use a Synology with Docker.

[Ordep]

I'm nearly throwing the towel in.

Could someone take a look at my log file and see if something odd?
output.log

[firecube]

My new echo show doesn't detect either but, as I read on another thread, if I plug my version 1 dot in too then the devices are detected and the show can control them.

[bwssytems]

@Ordep What is the ip address of your echo?

[Ordep]

@Ordep What is the ip address of your echo?

@bwssytems 192.168.1.134

[bwssytems]

So, the echo goes through the whole upnp process correctly, asks for the list of lights and then asks for light 1 (which is patio in your case). Then it seems to go through searching for the bridge again..... I am at a loss here too. Maybe it is not liking what is in the return of the light request. Will take a look and see if there was a change in the Philips API.

[NorthernMan54]

I was looking at this in detail as well, and found that it did go thru all my devices and stopped. What I did see that was odd, was that the echo had 2 threads talking to my code. One went thru the devices, and the other just asked for the description.xml and closed 13 seconds later.

My thinking is that the echo is calling one of the hue cloud API’s to check or validate something during the 13 seconds and that fails. Causing the discovery to fail. I did go so far as to use the exact response from my V1 hub as the response in my code, to downplay any API issues.

I also have a V1 round hue hub, and it works with the echo.

On Dec 21, 2017, at 9:18 AM, BWS Systems [e-mail] wrote:

So, the echo goes through the whole upnp process correctly, asks for the list of lights and then asks for light 1 (which is patio in your case). Then it seems to go through searching for the bridge again..... I am at a loss here too. Maybe it is not liking what is in the return of the light request. Will take a look and see if there was a change in the Philips API.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[bwssytems]

@NorthernMan54 Just to make sure I understand, in your Homebridge plugin for Alexa, it stops after it gets the device list and the fist device as well?

[NorthernMan54]

No, it goes thru all the lights and stops. ( the full device list ).

When I compared it to my Dot, it goes thru the lights, then the groups.

On Dec 21, 2017, at 9:46 AM, BWS Systems [e-mail] wrote:

@NorthernMan54 Just to make sure I understand, in your Homebridge plugin for Alexa, it stops after it gets the device list and the fist device as well?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[bwssytems]

@NorthernMan54 Interesting. Maybe a little network snooping will need to be in order.

[NorthernMan54]

Where are you thinking of snooping between? Echo and my code or echo and the internet? I was thinking about that, and trying to see if what else the echo is talking to during device discovery. And looked at the Philips API, which is https transport. And realized the most i might see is a ssl handshake.

It would prove my theory, but not get us any farther ahead.

I was actual thinking about going the skill based approach.

On Dec 21, 2017, at 12:09 PM, BWS Systems [e-mail] wrote:

@NorthernMan54 Interesting. Maybe a little network snooping will need to be in order.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[bwssytems]

@NorthernMan54 I do not have a 2nd gen echo so I am out for testing. And yes, snooping the echo IP and probably just the http packets would be the way to go.

[NorthernMan54]

Okay, I can do that but am away for a week.

On Dec 22, 2017, at 10:08 AM, BWS Systems [e-mail] wrote:

@NorthernMan54 I do not have a 2nd gen echo so I am out for testing. And yes, snooping the echo IP and probably just the http packets would be the way to go.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[bwssytems]

@NorthernMan54 No problem, we all do what we can when we can..... Thanks!

[roberteinhaus]

In a probably related case I had problems after throwing in a second echo. Everything was working well with my existing configuration with the two echos both able to use ha bridge devices until I added a new device to my configuration and started a new device discovery. It said it was not able to find any new devices. From then on, even the older, previously working devices were not working anymore.
Even after removing the new device and restarting the bridge several times I could not search for devices or use the old ones.
However I was able to fix it by disconnecting the second echo. Then I was able to find new devices and use them. Afterwards I reconnected the second echo and now I am able to use all the previously found devices.

[bwssytems]

@roberteinhaus That would be due to one of the echo's being a second gen.

[bwssytems]

Please go test RC version in #863

[NorthernMan54]

@bwssytems I spent a few hours trying to figure out how to sniff this. I was able to easily look at what was going thru my router from my echo gen 2, and didn't see anything except calls to the amazon cloud servers while running discovery. I'm still trying to get a sniff going on my wifi network to see if I can see anything else interesting.

[bwssytems]

@NorthernMan54 another reported issue in another thread gets the 2nd gne echo to the point of requesting the lights list, but then does not do anything after that. Another mention here was the discovering of scenes from the echo app then doing a discover devices.

[chrismillsuk]

Hi I have ha-bridge 5.1.0 installed on raspberry pi and after a few initial issues is working fine with echo plus , echo (2nd Gen) and 2 x echo dot(2nd gen) all in the same network.

When I started out with ha-bridge I only had the echo plus and I couldn’t get it to discover devices but I found if I did discover scenes, followed by discover devices from the app it worked. Since then if I delete all my devices in the app and ask any of the echos to discover my devices it finds all 6 ha-bridge devices.

[chrismillsuk]

I made a mistake the home bridge version is 5.0.0

[NorthernMan54]

@bwssytems Well I know a lot more about about sniffing WiFi networks then I did 2 weeks ago, but am no further ahead. ( Pro tip for sniffing a 2.4 and 5ghz network, your devices may hop networks so shut down one prior to sniffing. ). I see it getting the lights list, then the individuals lights then nothing. I think this is stuck until someone can discover what we are missing.

I did see some odd things with my hue v1 hub. First it is using http 1.0, and second my echo 2nd generation has stopped talking to it. It was working previously, but something changed to stop it. My dot still works with it okay.

[Pontihog67]

Hi,

I have been trying for 4 days to get the Echo to find the bridge. I am on port 80. I have purchased an Echo 2 dot that was just delivered today in hopes that could find the bridge, but no luck.

Can anyone assist with getting this to work for me? I am trying to use Alex10 on Windows with the bridge and the creator of Alex10 has tried to help me and referred me here.

I am just using X10 modules and a Bond ceiling fan interface. Alexa finds the Bond ceiling fans but not the bridge.r

I saw the messages in the closed thread about adding a scene, but I am unfamiliar with how to do that.

Any help will be greatly appreciated.

Thanks
Ponti

[bwssytems]

So far, there have been mixed reports on Echo 2nd Gen working. It seems you may have to wait until a software update comes to your 2nd Gen Echo and unfortunately, there is no control over when that occurs.

[Pontihog67]

Thank you,

I tried again this morning and for the first time I got a screen about pairing my lights (can't remember everything it said but it still said no devices found) Never had that screen before.

I guess I have to wait for an update as I'm not sure how to add a scene (even if I can with just X10).

Thanks for the help

[bwssytems]

So V5.2.0 is out there and it has an update for upnp sending. Please try and see if your echo 2nd gen is working now.

[Pontihog67]

No luck with V5.2.0 on my end. Both my Echo 2nd gen and Dot 2nd gen cannot find any new devices with this update.

[bwssytems]

@Pontihog67 Please check in the bridge control tab what the upnp send delay is set to?

[Pontihog67]

@bwssytems upnp send is set to 650

[bwssytems]

Try 500 and if that is not working go up to 1000 and see what happens.

[Pontihog67]

@bwssytems Tried 500 and 1000 and Alexa did not discover my bridge. Tried from the app also.

[bwssytems]

Just finished testing my Echo 2nd Gen and it finds the ha-bridge. One caveat for all of you out there. If you have 'Use Link Button' turned on in your security settings, you still need to hit the link button to get it to pair.

[Pontihog67]

@bwssytems Still no luck here. Must be something I'm doing wrong. I can click on the bridge on and off and my my units will cycle on and off. My firewall is open for java, but my echo 2nd gen will not find them.

Also a stupid question, do I need to enable a special skill in the echo for it to find the bridge? I already have the Honeywell skill for my thermostats and Bond skill for my ceiling fans.

I just feel Im missing something

Thanks for all of your help

[bwssytems]

No skills needed. It seems the 2nd gen is just a bit trickier on the discovery.

My scenario that seems to work:

** Make sure you have enabled the 'Use Link Button' in the ha-bridge security settings!

1) start discover on Alexa
2) press the link button on the ha-bridge 'Bridge Devices' tab
3) most likely this discover will not find anything
4) start discover on Alexa again
5) press the link button on the ha-bridge 'Bridge Devices' tab
6) after Alexa finishes, you should see your devices or new devices added

[Pontihog67]

@bwssytems Still no luck, I guess it just won't work with my version.
Thanks for all your help anyway.

[bwssytems]

@Pontihog67 One last thing to try is going down to 100 for the upnp send delay

[Pontihog67]

@bwssytems Oh well, no luck with that either. Has anyone else reported any success over the last couple of days?

Thanks again

[bwssytems]

@Pontihog67 There have been successes all along. I have a 2nd gen and it is working fine. Others have had success when I added the send delay. You may have other issues. Turn on traceupnp and try it and send the log and the ip address of your echo

[Jenjis486]

It happens the same to me.
I have HA-Bridge installed in a Docker container in a Synology
The configuration of HA-Bridge is 192.168.1.10 and port 8080.
The echo dot 2 has the ip 192.168.1.35

ha-bridge.log

[Pontihog67]

@bwssytems Do I turn on Trace UPNP Calls by clicking the false box?

I'm really not sure where to find the log file other than the log tab, but it doesn't look like the ha-bridge.log that is in the message above.

[bwssytems]

@Jenjis486 Port 8080 is not the suggested port to use. Please change it to 80.

@Pontihog67 The logs in the log tab will be fine. Jut cut and past it into a text file, then post.

[bwssytems]

@Jenjis486 You have an issue with your setup where it is using the 10.8.0.0 network.

[Pontihog67]

@bwssytems The bridge is running on 192.168.1.236 The echo is 192.168.1.122 The echo dot 192.168.1.171.

habridgelog.txt

[Jenjis486]

I can not use port 80 because Synology uses it, so I want to use port 8080
The 10.8.0.0 network is my vpn access to the computer, but the local network is 192.168.1.0

[bwssytems]

@Jenjis486 Well the first problem is your ha-bridge is picking up your VPN address, this needs to be configured in the settings to be your local ip address. https://github.com/bwssytems/ha-bridge/wiki/Trouble-Shooting#q-echo-does-not-discover-my-ha-bridge

[bwssytems]

@Pontihog67 You still need to turn on trace upnp in the Bridge Control Tab first. Then do a discover after so it generates the trace messages.

[Pontihog67]

@bwssytems. I guess you missed my question before. Not sure how to turn it on, I just see a clickbox for "false" for Upnp trace. Do I tick that?

Thanks

[bwssytems]

Yes

[Pontihog67]

@bwssytems

I'll try again

habridgelogmarch14.txt

[bwssytems]

@Pontihog67 you have this error:

03-14-2018 17:26:52.188     WARN    The upnp config address, localhost, does not match any known IP's on this host.     com.bwssystems.HABridge.BridgeSettings

So you did not follow the troubleshooting faq. You still need to set your upnp config address to the ip of your host, 192.168.1.236.

Also described in the readme here https://github.com/bwssytems/ha-bridge#upnp-ip-address

[Pontihog67]

Missed that! That was it, Thanks for all the help

[bwssytems]

@haymaan Is your issue resolved?

[haymaan]

Still can't discover any thing....change my HAbridge from Synology to raspberry no success

[bwssytems]

@haymaan please read the trouble shooting faq referenced above and install version 5.2.0

[haymaan]

Okey I'll reinstall and read it again..
Thanks will keep you updated

[Jenjis486]

Sorry,

I have done a clean installation on a Raspberry (192.168.1.11), where I installed Domoticz and HaBridge, this on port 80.
I'm still having the same problem. I attached the log file.
Maybe I have a problem with my Echo Dot 2. I buy it in the UK, but I have it working in Spain?

habridge-log.txt

[bwssytems]

@Jenjis486 I will assume the echo dot you have is on IP address 192.168.1.10. So you will need to try the steps in the Trouble Shooting faq for using the link button. It is the 5th bullet point in https://github.com/bwssytems/ha-bridge/wiki/Trouble-Shooting#q-echo-does-not-discover-my-ha-bridge

[Jenjis486]

No. The ip 192.168.1.10 in the NAS Synology, the IP of Echo Dot 2 is in the IP 192.168.1.35 and the HaBridge server in the IP 192.168.1.11.
When reviewing the log file, I have not seen this IP ask.
I do not know if it's configuration of my Echo Dot 2

[bwssytems]

@Jenjis486 Interesting, the echo dot is not even asking. This should happen. Is there some network settings to check on your router such as allowing upnp traffic?

[bwssytems]

@Jenjis486 This also needs to be considered if on a synology https://github.com/aptalca/docker-ha-bridge/issues/13

[originaltacos]

Hi everybody,

I have the same problem. HA-Bridge running on a Synology NAS on port 8081 (Port 80 is already used) without docker. Try everything from the trouble shooting guide except the Port 80 because I can't. My Echo dot (second gen) can't find the bridge. I'm running version 5.2.1.

Here the logs
Log.txt

[butsify]

Hi,

I run HA-Bridge 5.2.1 on a raspberry on port 80. I also tried the troubleshooting guide (IGMP off, UPNP on, 2x search,...), changed the UPNP delay, enabled the link button, recreated the device (currently, I just have one for testing) and still can't find the device in the Alexa app.

Under Manage Links, there is a Echo entry:

Echo#192.168.188.67 | 2018-03-18T20:28:20

I already removed it again, retried to find devices and the entry was there again.

Echo IP: 192.168.188.67 PI IP: 192.168.188.62

The device works in the web UI.

Logs (tried to find devices 3x this time):
habridge-log.txt

Thank you!

[Jenjis486]

I have several Philips Hue that has detected the Echo Dot 2 without any problem.

The only thing I have not managed to do is add Ha-Bridge, neither the Synology with Docker (port 8080), nor in the Raspberry (port 80).

I'm going to install a network analyzer and review the IP frames.

But reviewing the comments, I see that this problem we have enough users. In my case the Echo Dot buy it in the UK, although I use it in Spain, but configured with UK address

[bwssytems]

@Jenjis486 It seems your issue is about networking. Currently, all 2nd gen device issues are resolved. One question for you, are you trying to control a device on a remote network?

[bgeneto]

Just to let you know guys... my problem with ha-bridge v5.2.1 and echo dot 2nd gen not working was the firewall (iptables, in my case). Even after running on port 80, upnp delay set to 100, "Use link button" turned on, allowed tcp/udp ports 80 and 50000 etc... the discovery from Alexa app didn't work. I had to allow all traffic in my subnet in order to getting the devices recognized by echo dot 2. As this imposes a (small) security risk, I still would like to know the exact rules/ports needed to ha-bridge in order to communicate successfully with Amazon echo devices... Great job anyway.

[Jenjis486]

Good morning, I continue with my tests.
I installed Ha-Bridge on a raspberry (192.168.1.11) on port 80 and I have the Echo Dot 2 (192.168.1.35). When analyzing traffic on the raspberry using tcpdump, I do not see Upnp UDP discovery frames sent by the Echo (port 1900).
Other discovery frames of other computers are seen on the network, so the network is not cutting off that traffic.
All security is disabled.
I have set the Echo factory, so I do not know what else I can do.
I have the Echo configured in the UK, with my Amazon account in the UK.
If it occurs to you that can happen to me, I would appreciate it.
Regards,

[Jenjis486]

The only thing I do is set up the computer remotely, through a tunnel from my office, but I do the same from home and it does not work either.
The Echo Dot 2 discovered a Philips Hue gateway without problem.

[bwssytems]

@Jenjis486 So, Still confused here. IS your echo in a physical location at a home in the UK while your raspberry Pi is in a location in Spain over a bridged network?

[Jenjis486]

No. Alexa has not arrived in Spain. I bought the Echo DOt 2 in the UK; but I have it installed in Spain, in the same physical location as the raspberry.
The Echo is connected by Wifi and the raspberry by cable to a router Aus RT-AC1200G +.
I have registered the Echo in the Amazon account of UK to be able to use it and in that account I have the UK address. Yesterday I was resetting factory, but I could not finish the configuration.

[bwssytems]

@Jenjis486 Please post your ha-bridge.conf

[kesribath]

Hi guys, I have faced similar problems in getting Echo Gen 2 (India) to work with ha-bridge. However, I recently stumbled onto a solution. When I reverted my ha-bridge version to v3.5.1 (which was originally installed on my pi) from v.5.2.0 my Gen 2 Echo was able to discover devices immediately. I changed the installed version a couple of times more and the behaviour has been consistent - discovery works on v3.5.1 and fails on the latest.
EDIT: I forgot to add that the hue emulation is recognised by the philips hue app in both versions of ha-bridge..

[Jenjis486]

Good afternoon,
Sorry for the delay, but I have been on vacation and I have not been able to access the system.
I enclose the configuration of the raspberry and Synology.
habridge_synology.config.txt
habridge_rpi.config.txt

Regards,

[bwssytems]

@Jenjis486 You synology habridge is running on port 8080. Try port 80. Does your Pi habridge work properly?

[Jenjis486]

No. I have the same problem as Synology. I have Ha Bridge configured on the Raspberry, connected to Dmoticz, and I can not get my Echo Dot 2 to recognize any signal

[bwssytems]

@Jenjis486 If you would please, turn on tracupnp on your Pi and post the logs.

[bwssytems]

@Jenjis486 Also, don't forget the discovery while traceupnp is on....

[sarge31]

Is it possible to get a copy of a successful log showing a successful discovery. I don't get an devices listed in Alexa however it does allow me to control the devices added in haBridge with voice (dot 2). I'm assuming that it has discovered the devices but I just cant see them listed in Alexa. New to all this btw so apologies if I'm missing something.

[bwssytems]

@sarge31 So you do not see them in the alexa app or the alexa web page under smart home devices?

[sarge31]

@bwssytems Correct. They do not appear in the devices under smart home (app or web page) but are definitely recognised when I tell alexa to turn them on or off. I originally thought this was how it was meant to be since there was no skill associated but from reading this thread it seems I might have an issue.

[sarge31]

Disregard. Re-registered the dot and it now displays the devices under smart home.

[bwssytems]

I am closing this as the synology issue has been resolved. All discovery issues have been discussed as well and they all have solutions.