search

bwssytems / ha-bridge

Home automation bridge that emulates a Philips Hue light system and can control other systems such as a Vera, Harmony Hub, Nest, MiLight bulbs or any other system that has an http/https/tcp/udp interface. This is a compact impl to run on small format computers. This is impl started from this project https://github.com/armzilla/amazon-echo-ha-bridge.
Apache License 2.0
1.45k stars 198 forks source link

Amazon Echo 4 th gen new device discovery problems #1342

Open chang69 opened 2 years ago

chang69 commented 2 years ago

Hi all,

Just to let you know that I bought a new Echo 4th gen(the round speaker bowl) te place my first gen. I couldnt discover any new devices after delete the old ones. In the meanwhile upgrade to 5.4.1RC1 and turned on Octet 9. Renumbers. Still no luck, neither via the app, alexa website nor the echo 4th gen speaker.

I have removed all config files and db files, and did a clean initialization and rebuild all devices from Domoticz. Still no luck, the devices do show the proper 9 digit Octet.

Then I decided to connect back my Gen 1 Alexa to discover new devices and voila, all devices pop up as expected. After the devices are discovered I can turn them on and off via the new Echo 4th Gen.

I suspect that the Gen 1 device has a specific discovery aglorithm in the hardware?

Anything I can help to structurally solve this problem let me know.

sundown94 commented 2 years ago

Hi Everyone! I am experiencing what I believe is the same issue. About a week ago, my devices suddenly stopped working (Alexa responds with something like "Sorry, XYZ is not responding. Please check your connections..." I deleted all my devices on Alexa and tried to rediscover them all. None of them came back. I unplugged all my Alexas throughout the house and then tried discovery on each of them one-by-one (plugging and unplugging them all). Nothing worked. When I came here and saw this post, I dug through my box of electronics and found an original Gen 1 Alexa that I had previously upgraded with a Gen 2. I plugged it in, tried discovery and wow, all my devices were back again!! So a Gen 1 Alexa did work for me too. However, that is until I noticed the blue ring spinning around on the Gen 1 and then it rebooted itself. I think it went through a software upgrade (since this was the first time I had it plugged in for several years). After it rebooted, my devices no longer work again. I am back to square one. And if delete everything and try discovery, nothing is found. So unfortunately, this solution worked for about 10 minutes.

Any help would be greatly appreciated. Or let me know if I can help in some way (e.g., testing, etc.).

Also, forgot to mention that I am using HA-Bridge 5.4.0. I was using 5.3, but updated to 5.4 when this happened, and still no luck.

chang69 commented 2 years ago

Hi Everyone! I am experiencing what I believe is the same issue. About a week ago, my devices suddenly stopped working (Alexa responds with something like "Sorry, XYZ is not responding. Please check your connections..." I deleted all my devices on Alexa and tried to rediscover them all. None of them came back. I unplugged all my Alexas throughout the house and then tried discovery on each of them one-by-one (plugging and unplugging them all). Nothing worked. When I came here and saw this post, I dug through my box of electronics and found an original Gen 1 Alexa that I had previously upgraded with a Gen 2. I plugged it in, tried discovery and wow, all my devices were back again!! So a Gen 1 Alexa did work for me too. However, that is until I noticed the blue ring spinning around on the Gen 1 and then it rebooted itself. I think it went through a software upgrade (since this was the first time I had it plugged in for several years). After it rebooted, my devices no longer work again. I am back to square one. And if delete everything and try discovery, nothing is found. So unfortunately, this solution worked for about 10 minutes.

Any help would be greatly appreciated. Or let me know if I can help in some way (e.g., testing, etc.).

Also, forgot to mention that I am using HA-Bridge 5.4.0. I was using 5.3, but updated to 5.4 when this happened, and still no luck.

Mine gen 1 still works, it doesnt update any firmware or stuff. After detecting the devices I can use the gen 4 to control them. But the weirdest thing happened today, I couldn't control the devices anymore. It keeps saying that the devices dont support the action.

Also please try 5.4.1RC1 and turn on use Octet 9 and Renumber.

sundown94 commented 2 years ago

Mine gen 1 still works, it doesnt update any firmware or stuff. After detecting the devices I can use the gen 4 to control them. But the weirdest thing happened today, I couldn't control the devices anymore. It keeps saying that the devices dont support the action.

Also please try 5.4.1RC1 and turn on use Octet 9 and Renumber.

Thanks for the tip. I finally had some time to play around with this again, and downloaded the 5.4.1RC1.

I should take a moment here to clarify that my old Echo device that I used might have actually been Gen 2 instead of Gen 1...is there a way to tell from looking at it? The reason I no longer use it is because it goes into a constant loop of rebooting itself after it warms up (it is basically broken). So the other day when I did plug it in, it ran fine until it warmed up, during which time it initially discovered my devices, did a firmware upgrade, and then no longer recognized my devices. Shortly thereafter, it started it endless reboot loop and I was back to square one.

So now that I installed 5.4.1RC1 tonight (and only have Gen 2 and newer devices on my network), everything seems to be working again. I should add that I switched to Octet9 and Renumbered everything as you requested before hitting the "Discover Devices" button on the Alexa website. Since it has been a few days since the problems started happening, I suppose Amazon could have fixed it on their end, but assuming they didn't then it would seem your advice did the trick for me...for now. And for that, I must say "thank you!!!!" for the help!!!! Did yours "magically" start working at this point?

jayjupdhig commented 2 years ago

Maybe similar to: https://github.com/bwssytems/ha-bridge/issues/1351 ?

steviehs commented 2 years ago

1216 gives more hints about all this. My final solution is to put all non gen1 echos behind a filter... :-)

Flawkee commented 2 years ago

I have a single Echo dot 4 and nothing else. Discovery doesn't work. tried using V5.3.0, 5.4.1. Currently running on 5.4.1C1. 9 Octets enabled. It seems like the HA-Bridge received the packets from the echo 4 and sends a response but the discovery do not work.

06-07-2022 19:39:06.146 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.1.126:80 to address: 10.0.1.123:50000 com.bwssystems.HABridge.upnp.UpnpListener 06-07-2022 19:39:05.496 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.1.123:50000 com.bwssystems.HABridge.upnp.UpnpListener 06-07-2022 19:39:05.495 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.1.126:80 to address: 10.0.1.123:50000 com.bwssystems.HABridge.upnp.UpnpListener 06-07-2022 19:39:04.845 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.1.123:50000 com.bwssystems.HABridge.upnp.UpnpListener 06-07-2022 19:39:03.505 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#10.0.1.110 and username: 2ce683986320439d9c4bf2902b18d426 com.bwssystems.HABridge.hue.HueMulator 06-07-2022 19:39:03.174 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.1.126:80 to address: 10.0.1.123:50000 com.bwssystems.HABridge.upnp.UpnpListener 06-07-2022 19:39:02.524 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.1.123:50000 com.bwssystems.HABridge.upnp.UpnpListener 06-07-2022 19:39:02.523 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.1.126:80 to address: 10.0.1.123:50000 com.bwssystems.HABridge.upnp.UpnpListener 06-07-2022 19:39:01.873 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.1.123:50000 com.bwssystems.HABridge.upnp.UpnpListener 06-07-2022 19:39:00.103 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.1.126:80 to address: 10.0.1.123:50000 com.bwssystems.HABridge.upnp.UpnpListener 06-07-2022 19:38:59.452 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.1.123:50000 com.bwssystems.HABridge.upnp.UpnpListener 06-07-2022 19:38:59.451 INFO Traceupnp: send upnp discovery template 1 with response address: 10.0.1.126:80 to address: 10.0.1.123:50000 com.bwssystems.HABridge.upnp.UpnpListener 06-07-2022 19:38:58.801 INFO Traceupnp: SSDP M-SEARCH packet from 10.0.1.123:50000

Echo dot 4 IP is 10.0.1.123