ha-bridge incompatible with Amazon Echo Dot Gen. 3? #1092
Comments
|
additional info: what we do is an emulation of philips hue devices with ha-bridge |
|
There should not be any issues. Did you turn on traceupnp to see if the ha-bridge can read the echo's UPNP messages? |
|
Where can i find the "traceupnp" logs? Thx for feedback. |
|
There are 5 emulated philips hue lights, they will not be found anymore with echo dot gen. 3. With echo dot gen. 2, there are no problems... I set "traceupnp" to "true", and log level to "trace". After that, i started a smart home device search on amazon's alexa website. Log is here: |
|
The version i use is 5.2.2. |
|
What is the IP of the gen 3 echo? |
|
192.168.1.130 (this is my business account, "jmar83" the personal) |
|
A few facts:
So, the devices will be bound on the second try. But when i say "Computer, Licht Büro einschalten" (which means "Computer, turn on light office" in german ;-)), the device will not be found. No connection. Also with ha-bridge on port 80. The link button in ha bridge gui seems to be effectless when i search for smart home device on alexa website. No difference so it seems! |
|
There seems to be a lot of issues with the current ha bridge and some alexa device (no just echo dot gen. 3!), there there is not one "step-by-step" manual in the whole internet to make it run. Also the problems (and potential solutions) are VERY VERY different when i look on that page: #1022 Some of them seems to run (and the people don't know why), others not...(and the people also don't know why ;-)) |
|
Additional info: The amazon echo dot gen. 3 i have was bougth in switzerland. Account was also set to switzerland. |
|
No answer...? |
|
Or no solution, so it seems?? |
|
So, how are you running the ha-bridge (startup config)? what platform are you running on? |
|
"java -jar ha-bridge.jar" on raspbian stretch with most current updates. and i changed some logging options (upnp and general log level) in the ha-bridge gui... |
|
what about your network setup? |
|
I will be adding an older style upnp message to see if that helps. Others had success with going back to v3.2.1 which used a different upnp message style. |
|
Now i've done some research: With Gen. 3 Echo devices, the smart home device search process on alexa website seems to work like a random generator... sometimes it found (some) devices, sometimes not. (And sometimes i have devices in the list i never had, e.g. "Bad" (which means bath). And also the echo device is in the smart home device list. (I never had that with Gen. 2) If they will be found, i'm able to switch them when i run the HTTP daemon on port 80. (That behavior must be implemented from Amazon, so we can't change it.. e.g. with Port 81, it does not work while Gen. 2 works without any problem. And i didn't test Gen. 1, no idea how it works) My Network setup: 192.168.80.0/24
The reason for the virtual network controller is the fact that on the physical adapter's IP an apache2 service is running for our web GUI. |
|
same Problem with 5.2.2 - workaround old alexa as proxy to discover the devices |
|
The only port 80 for gen 3 devices problem is amazon's work, but the device search (UDP uPNP) could be a problem of habridge. In my case, the first search don't show any devices, then i need to search again in 5-7 seconds, then the devices (sometimes) will be found |
|
if you have a webserver that already needs port 80, then set up a virtual lan adapter (type "macvlan") to run ha-bridge service on it with port 80 |
|
Is it compatible with ECHO Input ?. LOG |
|
I think there are problems with gen. 3 device. What generation is your "Echo Input" ? |
|
It's a new device, without a speaker, so, i imagine the latest generation... |
|
Gen. 3 devices require that ha bridge runs on port 80, then the switch works without problems - as long the device search was successful, but it is not always... I think there is more a problem with the method that ha-bridge is using to emulate philips hue devices. (On UDP / uPnP layer), so they won't be found sucessful. Mostly i need to start 2 device searches, with a minimal pause of 5-7 seconds.. |
|
Ha Bridge uses port 80. Repeated searches do not work either |
|
@gcaruncho In your trace above, what is the IP address of the Echo Input? |
|
Alexa Gen. 3 devices use Port 80 (only). HA-Bridge can be configured with different ports, e.g. 81 that works with Gen. 2 devices for example |
HA-Bridge IP 192.168.1.42. Port 80 (Domoticz is in the same Raspberry Pi 3) |
|
@gcaruncho I do not see in your log where the alexa is even trying to discover the ha-bridge. There should be a message from the ip address of 192.168.1.60. Please do multiple discover devices from Alexa while you have the Traceupnp on. Your current log only shows one minute of running. |
Fixes #670 Execute select Device when bridge loads [Enhancement Request] enhancement Fixes #877 Color in Hue/Sat enhancement Fixes #917 lock device ID #s enhancement Fixes #1032 Support for HomeGenie enhancement Fixes #1033 Backup & Restore enhancement Fixes #1060 Voice command colour change bug question Fixes #1077 several somfy action in a same Row ID doesn't work bug question Fixes #1084 Add Mozilla IoT gateway Helper enhancement Fixes #1092 ha-bridge incompatible with Amazon Echo Dot Gen. 3? enhancement question Fixes #1093 Alexa Issue : ID conflict between HA Bridge an Hue Bridge enhancement question Fixes #1094 issue with 5.2.2 and Harmony enhancement question Fixes #1095 issue with 5.2.2 and fhem enhancement question Fixes #1098 Home Assistant has new authentication methods and Legacy API Passwords will be removed enhancement question Fixes #1103 Have single scroll bar for Bridge Devices page. enhancement Fixes #1108 Add mDNS Discovery to ha-bridge Fixes #1109 Add HTTPS to ha-bridge
We are developing a home automation system, until now we used the Amazon Echo Dot Gen. 2 without any problems.
Now we tested the Gen. 3 version... but so it seems, it does not work anymore with.
Are there any compatibility issues with the current ha-bridge version 5.2.2 and Amazon Echo Dot Gen. 3?
(The configuration of the device (Amazon Account) was successful - without any problems..)
Thank you for your feedbacks.
The text was updated successfully, but these errors were encountered: