Alexa device discovery now broke #1243
Comments
|
I think the issue resides with Amazon pushing some sort of update. |
Yeah. I don't mind re-creating my devices in v4.x.x but when I use v4 I get the bug whereby I can't add new devices as it overides the older devices |
|
I just tried using 4.5.6 and devices were still not discovered. |
|
I have same problem with a completely new installation 5.3.0 and 5.3.1rc1 - never used HA-Bridge before. I thought it may be an echo problem so reset it to factory defaults before testing but devices that are correctly defined in HA-Bridge are not discovered by Alexa app. |
V4.x.x always worked well for me. Just had too many other bugs. Maybe it's some other issue for you. Firewall? Different subnet, port? |
|
Echo and HA-Bridge connected to same router/subnet, and I can see udp traffic between them so unlikely to be firewall. |
Did they find a fix, is there a link? There is an option to increase a timeout but perhaps not the correct thing. We could try increasing the timeout to 2000 or 3000 |
|
No sign of a fix yet sadly |
Still, v4 works for me. How odd |
|
Hello
|
|
I also tried HA-Bridge 4.5.6 with a clean install, created a device but still discovery didn't work. Tried with 2 versions of echo dot and a full sized echo. |
|
Also seeing the same issue (adding new devices) with 5.3.1RC1 Foolishly deleted all my HA-Bridge devices from amazon smart home devices, thinking they'd all return. But nothing detected. Tried re-installing Gen2 Dot, Gen 3 Dot and Show 8 then re-discovering. No luck. Then I saw this post regarding V4.x.x, so installed V4.5.6 deleted all in ha-bridge/data directory, added a few dimmable lights but was still unable to add new devices. That was last night. Just for the hell of it ran another discover earlier today, and 3 lights are detected and controllable okay, and one was detected but duplicated. I think one of the duplicates might have been working but I managed to delete the wrong duplicate! Doh! Tried to add the deleted duplicate to no avail. I then restored V5.3.1RC1 using the /data db and config files as created by 4.5.6, and my 3 working lights are controllable by Alexa. I then tried adding my previously duplicated light, (still with V5.3.1RC1) but it is still not discovered. Currently sticking with my 3 working lights until Amazon resolves this issue whenever that happens to be. So I can confirm for the sake of smartypantsuk sanity that V4.5.6 sort of worked for me but only after leaving things for about 12 hours before performing a re-discovery. (Some sort of caching thing at the Amazon Alexa device back-end?) |
The funny thing was i tried v5.3.1.RC1 again last night and it found 2 new devices. Then it wouldn't find anything else after that. However, you could be right about the caching issue because one of the devices that it found did not exist in the HA-bridge database. It was a test device that I created but then deleted probably a few hours previous. So where did this ghost device come from if not some cache. |
|
@smartypantsuk - Re. caching... With regard to my duplicate light I mentioned above, I'm guessing one of them was discovered earlier (under 4.5.6) the other (which did not work from Alexa voice or the Alexa Android App) must be lurking in the cloud somewhere. I definitely reset all of my devices, which presumably clears any on-device stuff? Who knows? It's interesting that Alexa discover via 5.3.1RC1 managed to pick up any devices. I have had zero success. |
|
The guys over at Misterhouse think Amazon have changed the protocol to not use gzip in the header requests during discovery. They are going to do some more testing. It seems devices already discovered may continue to work, but once deleted you can only discover them again if they are in a cache somewhere. I think this is going to need someone from HA-Bridge to snoop the network with a real Hue device to see what should be going on and then patch HA-Bridge accordingly, I don't see Amazon helping here unless they cannot discover real Hue devices themselves now. |
|
Seems very odd. I have some hue stuff here and a signed sniffer but I've decommissioned everything at present. Really like the hue lights but not zigbee in general. It's a shame they didn't go zwave with the hue system. I digress. Is ha-bridge even developed anymore? |
|
most recent release was 26 Mar |
|
@bwssytems Is this still developed? |
|
I have the same problem with 5.3.0 - Added a new device yesterday and when it wasn't discovered I foolishly removed all devices in the hope that would clear the problem. Alas it only made it worse, now Alexa refuses to find any of my devices that are defined in HA-Bridge. After several discoveries, similar to someone else who commented, one of my devices re-appeared but nothing in it's definition is in anyway unique . Here's hoping for a solution. |
smartypantsuk
changed the title
|
Okay I've edited the title to better reflect the problem. After further testing it appears that No versions are working with respect to discovery. |
|
I can confirm that issue. I can only guess, maybe Amazon wants to force us to write an Alexa Skill for that? |
|
I have never had discovery issues very long time user of HA-Bridge, even swapped out routers a year ago without issue (Verizon to Asus). I tried adding a new test device and my echos are able to discover the device. (Gen 1 Echo, multiple Gen 1 & 2 Dots, Gen 1 & 10.1" Premium Show, Gen 1 Spot) However the alexa smart home page is surely going through changes, the page will change for me to one I've never seen before following these steps (but not every time):
Anyone else seeing this combined page? |
Can you confirm the bridge version you are using and try creating a new test device to see if that discovers as of now? |
|
On an associated note, these changes by Amazon may be related to a development brief I read a few months back. Specifically, that coming soon would be the ability to use some smart home skills offline! In other words, some skills for controlling your smart home will not require to be online. This would be useful and may allow a custom skill to work similar to ha-bridge. But maybe not. Time will tell. |
|
After deleting devices from here https://www.amazon.in/hz/mycd/myx#/home/alexaPrivacy/deviceHistory, I was able to discover devices but with delays, patience needed, as highlighted somewhere in the thread it takes some time to clear cached devices, to be on safe side I did a 20 sec reboot for the Echo Plus. |
|
Hello |
|
Ok, so I added a new device in my habridge to day (5.3.0) and I stumbled on the fact it is not added (discovered) by alexa. "old/existing" devices do work but no new discovered. And then I stumbled on this topic... But I am not seeing a solution yet, correct? |
|
Correct, I've emailed [email protected] and [email protected] and got no reply. |
|
So this means this ENTIRE project is not functional anymore!? That would be the worst news before christmas after covid :-). @bwssytems can you please advise? |
|
I didn't want to recreate all the devices so I edited the devices.db |
|
Thanks to everyone involved in this fix. Spent an age chasing multicast traffic across my network. Found this thread, updated in about 45 seconds and all sorted. PHEW C |
|
I gave up on using habridge directly with Alexa several months ago. One by one the devices "stopped responding" and usually couldn't be re-discovered even if deleted. What I found, however, is that Smartthings can readily discover habridge devices and then Alexa discovers them from Smartthings within seconds. It means an extra step in that Alexa talks to my Smartthings hub, then the Smartthings hub talks to the habridge, but the delay is not noticeable. Everything just works including dimming. Interestingly, the Smartthings server takes the habridge device unique ID, eg uniqueId: 00:17:88:5E:D3:C8-00, and converts it to the form 02420A010A40/200 where the base number (before the slash) is the ID that Smartthings assigned to the habridge and 200 is the device ID. All of the child devices of the habridge share the same base id number. It advertises the device through the Smartthings Alexa app and Alexa discovers it immediately and without being asked to discover devices. |
|
Interesting. My HA Bridge has been pretty much rock solid. Where I have had 'Device is not responding' it's where I've managed to get duplicates. C |
|
This worked for me (the RC2 update) I had to delete my "data" directory after updating my .jar to the RC2 version and then recreate all my devices. A pain, but it worked. Thank you to all who have (and continue to) contribute to this essential project. You all saved me from the wrath of my wife who was giving me the evil eye because the bridge was broken :) |
|
I've used HA Bridge with Homeseer under windows 10 for years. I've always run it on port 85 until it stopped working a few days ago. Wouldn't discover any devices and therefore lost echo control of approx 45 events and devices! |
Ha-bridge works on whatever port you specify, Alexa, however, doesn't. Amazon changed the discovery behaviour some time ago so that it only discovers on port 80. |
|
Pretty sure that's not quite right. AFAIK Alexa is using UPNP so port number is not really an applicable concept. However, I can categorically state that my HA bridge is running on 8080 (and UPNP response 5000) and with the new .jar discovery was working fine this week. Of course, it might have changed since Tuesday. |
There are some oddities that can't be quite explained regarding Alexa discovery. What works for some doesn't for others, however, port 80 became the necessary change many months ago. |
|
Aye. Does seem there’s some black box and inconsistencies around!
--
Chris Matthews
[email protected] <mailto:[email protected]>
https://www.linkedin.com/in/cmatthewsitdirector/ <https://www.linkedin.com/in/cmatthewsitdirector/>
+447964 207823 / +447855 823629
… On 29 Nov 2020, at 09:48, smartypantsuk ***@***.***> wrote:
Pretty sure that's not quite right. AFAIK Alexa is using UPNP so port number is not really an applicable concept. However, I can categorically state that my HA bridge is running on 8080 (and UPNP response 5000) and with the new .jar discovery was working fine this week. Of course, it might have changed since Tuesday.
It does look as though there's been another upgrade (but trying to remember versions is probably not going to work) so if discovery as suddenly stopped working (again) there might be an issue
There are some oddities that can't be quite explained regarding Alexa discovery. What works for some doesn't for others, however, port 80 became the necessary change many months ago.
Discovery stopped working for many and using port 80 fixed it. Maybe it's a hue requirement and not Alexa, but Google home also required the bridge to run on port 80.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1243 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQCZZNFSB3GNTUQCGHMWJ63SSIKFTANCNFSM4THLD75Q>.
|
|
So, for discovery to now work, it seems you need to delete all devices in the alexa echo app or home page. Make sure you are using 5.3.1RC2 and renumber your devices with a new seed in the bridge control tab. Then you can re-discover devices. |
|
Wow. Is that new behaviour from last week?
C
--
Chris Matthews
[email protected] <mailto:[email protected]>
https://www.linkedin.com/in/cmatthewsitdirector/ <https://www.linkedin.com/in/cmatthewsitdirector/>
+447964 207823 / +447855 823629
… On 30 Nov 2020, at 17:40, BWS Systems ***@***.***> wrote:
So, for discovery to now work, it seems you need to delete all devices in the alexa echo app or home page. Make sure you are using 5.3.1RC2 and renumber your devices with a new seed in the bridge control tab. Then you can re-discover devices.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1243 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQCZZNHRWKWCEFATQHTFZE3SSPKKFANCNFSM4THLD75Q>.
|
|
RC3 is now out in the releases section. Updated upnp handling and device unique ids to be more specific. Also it seems the unique ids have been too long since inception and that may be the root cause. Delete all your devices in alexa and use renumber before you discover. |
Dev branch 5.3.x to create v5.4.0 #1044 Alexa app, error "Device doesn't support requested value" bug question #1118 Device status update in Alexa App is not working correctly for ha-bridge devices bug duplicate question #1126 Can't get XY ColorData into URL enhancement question #1127 Can't get separate hue, saturation and brightness enhancement question #1128 Wrong color calucation in HS mode bug question #1131 Changing color temperatur is not working correctly bug question #1132 Conversion from CIE to RGB incorrect bug question #1139 Device ID creation fails bug question #1150 Home Assistant gets null exception during initialization bug question #1170 Alexa not sending the correct color codes duplicate #1171 Please add option: If bright request present with on, only send dim enhancement #1184 Alexa will not discover HABridge question #1191 When "Use UPNP Address Interface Only" is selected, echo cannot find ha-bridge bug #1210 [Enahnacement] Have link button timeout be configurable enhancement #1215 Alexa unable to discover recently added devices to ha-bridge duplicate question #1227 Feature request: ${intensity.previous} value passing control enhancement #1239 HA-Bridge has suddenly given up itself - Exception in thread "main" java.lang.NullPointerException bug question #1243 Alexa device discovery now broke question #1253 HABridge hue ColorDecode 0 0 0 bug question #1256 Homeassistant devices not appearing bug question
I have had this "Device is not responding" comment from Alexa when I have some how managed to get an entry in the "Dim item" line and I am trying to switch a heyu appliance module with no Dim possibility. The Entry in the Dim item line was simply an empty pair of square brackets... [] Removing that erroneous Dim Item and the Device is Not Responding response went away. |
|
Thanks I had the square brackets but deleting them has made no difference. Seems that many of my devices also have them and there’s no impact.
Very odd
C
--
Chris Matthews
***@***.*** ***@***.***>
https://www.linkedin.com/in/cmatthewsitdirector/ <https://www.linkedin.com/in/cmatthewsitdirector/>
+447964 207823 / +447855 823629
… On 25 Apr 2021, at 18:17, npaisnel ***@***.***> wrote:
Interesting. My HA Bridge has been pretty much rock solid. Where I have had 'Device is not responding' it's where I've managed to get duplicates.
The discovery is a bit of a PITA, but I don't change stuff often enough to worry about.
However I have no experience using it outside of openLuup. Alexa and Vera was atrocious (well Vera and anything, really)
C
I have had this "Device is not responding" comment from Alexa when I have some how managed to get an entry in the "Dim item" line and I am trying to switch a heyu appliance module with no Dim possibility.
The Entry in the Dim item line was simply an empty pair of square brackets... []
Removing that erroneous Dim Item and the Device is Not Responding response went away.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1243 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQCZZND2VR3QRDHPANQOV7TTKRFCVANCNFSM4THLD75Q>.
|
|
I did notice that even the new ID's have the -XX at the end and not the :XX yet it all still seems to work with the dash. |
|
I am new here. |
Amazon Alexa devices will only look for devices on port 80. Simple as that. The few discrepancies from posters on here who say their systems are working on an alternative port must have 1 or more Alexa devices either stuck on an old software version or the device hasn't updated properly, which may be yet another kind of caching issue, which seem to plague Alexa devices. You could of course setup reverse proxy. Some examples are on main page |
|
Thank you. I am working on reverse proxy server, actually, nginx IS the process holding port 80 on my Ubuntu server, should be easy to do. |
and others
Hi,
I have been using v5.3.1RC1 for a while, everything has worked well and the 'new device overwrites old device' bug has been fixed.
Sadly, and strangely, all my Alexa devices will no longer discover new bridge devices. After much diagnosing I have determined it to be a compatibility issue, possibly caused by an Amazon device update?
Testing:
Any v5.x.x version of the bridge does not allow for discovery. The logs show search and response between Alexa device and bridge but nothing is ever found on the Alexa device.
For reference I'm using ha-bridge on Windows 10.
Thanks
The text was updated successfully, but these errors were encountered: