Amazon Echo still not recognize 5.4.0 #1270
Comments
|
Did you use the "Link" Button or is it deactivated in your security settings? You could try adjust the ID SEED to 400 and then renumber devices. Then search again. |
|
Thanks i already test to renumber and change the ID SEED |
|
Turn off the link button in the security settings. Turn the trace upnp calls on in the bridge control. Post the output of the log after you do a discover from alexa |
|
I have link button off. I found 55 devices - and they still don't respond. |
|
Did the same thing - renumbered devices in bridge, deleted all devices on Amazon's site, found 55. Now I can't get them to respond. Logs below: Time
|
|
what's the ip addresses of your echos? |
|
No idea I have a bunch and they’re all dhcp so it’s a 192.168.2.x address. All of them are. |
Hello @bwssytems My alexa echo is 10.0.0.20 ip address HA-bridge on 10.0.0.21
` |
|
It s i thinks same problèm as #1272 It generate are with - and not : |
|
@bwssytems |
|
Hello Jean-Mercier: My alexa echo is 10.0.0.20 ip address
|
|
@bwssytems. |
|
Have a look at my post here #1272 (comment) to edit your |
|
Thanks for pointing this out, however i had this issue also with non 0 leading dev IDs. so my dev IDs were just straight from 1 - 24. |
|
@sonypsx |
|
Code below stops the bridge, makes a copy of your device.db file, then removes all "dash,digit,digit" combinations, then restarts the bridge. |
|
@audiofreak9: |
|
Thanks i can t try it now but i will in two week After holidays ;) |
|
I was able to get discovery of new devices to work by just changing the uniqueid as stated above without SEED change. You were able to get discovery by changing the SEED number in settings. So this tells me that it is indeed an Alexa cache issue using a combination of the id and uniqueid. If one or the other (or both) is changed the device(s) are discovered. This may also explain the return of previously deleted devices during discovery. @bwssytems: |
|
I ran into this as well. Once I renumbered and rediscovered with duplicates, I started deleting the duplicate devices then did a rediscover. Had to do this multiple times but it resolved that cache issue. Alexa wants the devices deleted while the ha-bridge is up and running as it seems to try to validate them. The old numbers cause a problem, but as you mention are cached. The perfect way to do this is to delete devices while the ha-bridge is up before any renumbering, then do the renumber and rediscover. |
|
I could find no way to directly clear the Alexa device cache, so following the advice from the bwssytem post above,
|
|
Hello happy new years to you !! this not work for me alexa don't discover any device i try to edit unique id to replace - by : but same problem alexa don't found habridge device |
|
@Jean-Mercier Did you reseed the device IDs? From the Bridge Control page, scroll to the bottom, find the "ID Seed" input and change it to something like 400. Then click Save at the top. When it reboots, from the Bridge Devices page click Renumber Devices. Then re-run discovery. If discovery is successful, from the Bridge Devices page click the ID number for your devices to "lock" them, they will turn bold when locked. |
|
Another help discovering devices and avoid the dupes: I have played now around a couple of hours. With rebooting Alexas, clearing devices restore, and renumbering. Total 6 pieces of Alexa However it does not make a difference by unplug them from power. What i also found out: I do have several TASMOTA Plugs running in "Belkin WeMo" Emulation mode. I have not added them to habridge, they got discovered on their own by alexa and it doesn't matter how many alexas are online, they always discovered correctly by one at a time. Maybe this is a hint for @bwssytems to sort some things out. Good luck for all those having dupe devices! |
|
sonypsx, I think your 6 dupes and 6 Alexas is a coincidence, but I wouldn't bet a lot of money on it. |
|
@trpster: Your fear by changing something is correct. I just ran into it. One device on habridge did respond with a 404 error even with the Testbutton. Reboot habridge, test again -> works fine - delete just that one device and add it again -> headbang! |
yes i try it still no device |
|
Hey it worked Better still...I then did a move of the old devices.db file from the databkp folder to the data folder and did a 'reinitialise' from the WebGUI Al the old devices re appeared..adn Alexa discovered them... So for me..for now Problem dissolved. @Jean-Mercier
then reboot t Then if it does move your old device database back |
|
YEAHHHH! congrats! I am happy to hear that! |
|
That's terrific news, and also explains why my stuff started working after I installed ha-bridge from scratch on a different r-pi. |
|
I will copy and post BOTH HABRIDGE config files and maybe some one better than me can find the clue going to be difficult I guess... as it has been fiddled with to try and get it working... and it was working with what should have been standard default config before |
|
OK, so here are the two habridge.config files old not workgin one first There are some differences, but they are only changes I have made AFTER the fault occured. The two differences are Securtiy data and the Hue Address line is an extra in the old version. Old one first {"upnpconfigaddress":"192.168.1.49" and the new working one {"upnpconfigaddress":"192.168.1.49" |
|
OK, so the only difference I can see are the Security data and the old file has an extra line "hueaddress":{"devices":[]} the other changes like hub version, upnpsenddelay linkbuttontimeout, etc are all changed on ly AFTER I treid to fix the not working SO the old file has an extra line and different securtiyData. Other wise all is the same |
|
I can not understand it! I have STOPPED the bridge - deleted all devices - rediscover and all devices are found. No no no idea how or where they are being found but it is frustrating! |
|
My advice, based on zero data, is that if things are working well, backup the ha-bridge.config file. |
|
I am running on mac osx and I have 100% stopped the HA-Bridge.java. I also removed all my devices by starting a new Data directory as someone suggested above. |
|
My server is down. I can't connect to it and it STILL find devices even the next day. Something screwy is going on! |
|
I've been on and off trying to get this to work since Christmas time. I tried a brand new install on a pi and still haven't had much luck. I kept getting stale entries popping up in my Alexa devices even after deleting it multiple times. Eventually after not trying for a bit, the stales aren't coming back but since trying to get this on a new pi, even trying a windows build, I can't get anything to be picked up by the Alexas anymore from habridge. I'm glad I'm not seeing the cached items anymore but I'm not sure what else I'm missing. These are brand new from scratch builds with no configs, and nothing else on the pi to mess with anything. On the Alexa side of things, I've now deregistered all my Alexas and reregistered them(above mentions logging out, I believe this is the term they mean, I don't see a logging off option anywhere, on the website or the app on my phone, only a deregister). I'm not having much luck.. |
|
It is a total nightmare and if you have done a clean install, the fix I succeeded with of of deleting the data file is not going to help. All I can think to try ..if you have not already tiried is to NOT use the Link button. When I succeeded I did not use the Link button. |
|
I can only get my alex's / echo dots and all are storing the devices in cache? I've thought about using a new email or shutting them all down but I have A LOT. |
|
My link time is set for 45 seconds; I suppose it's the default because I never set it. |
|
I do not need to use the Link button I just tried it I created a new device and Alexa found ti immediately ...no need to Press the Link button. Try without using Link |
|
I finally got this. Enabling the trace upnp helped me understand what was going on better. All my devices were being seen, just not connecting really. I switched the web server port from 8080 to port 80 and that was the fix. All my devices are connecting now. Phew. |
|
@kllngtme Yes Amazon has changed discovery to only work with port 80. This occurred more than a year ago. |
|
Well I can say one thing about the 'fix' of deleting the data folder...is that is a one time fix...I have tried it again when Alexa some how came up with a new error "Can't find device or group named X in Y's profile" So I tried a Discover devices..no go So went back both fix that worked last week. Backup the /habridge/Data folder to a different name..and re boot the server so it created a new data folder This time. on re creating new devices..I does not find them. So the Fix of deleting Data and start gin a fresh 'system" was merely a fluke. Maybe it is just a matter of leaving Alexa alone for a week or so ...so it flushes old data out of a cache some where.... dunno..but the fix is not a real fix..it was just a lucky coincidence! |
|
Another update. MY Alexa stopped responding and seeing any devices that were already found when I Accidentally Hit the Setup Remote button on the iPhone App. After hitting that and quitting out of the app...Alexa did not see the devices.. No amount of re booting or other tricks would see them again. Just got a messages from Alexa saying .. Last night before I went to bed I de-registered both Alexa devices. Give them 10 minutes and they start flashing orange and you can set them up again. I also Deleted the data file from habridge directory Rebooted and then copied the devices.db file back to data. Diaan "Alexa Find new devices...and all 26 were found again. Maybe the trick is to deregister the Echo devices and leave it all for a few hours..over night,,, Dunno ... But if you get stuck, worth a try . |
|
@npaisnel: |
|
I deactivated all my echos like you guys suggested and finally found no new devices. Then I had to get everything working again and my installation of HA-Bridge is / was a mess. It still is. The problem is almost no one here is using Mac OSX to run this so I don't have a good reference on HOW it should be configured. I finally was able to get OLD files to reload by rebooting EVERY time. I don't know why I have to reboot but the devices and config files will not stick unless I reboot. My files were PRE moving to port 80 for the webserver. I am at the point where Amazon can not find any of my devices. Nothing gets discovered. Don't know why and kinda don't care anymore. I gave it the good try - but frustration and lack of being able to control this stuff - it just isn't worth the trouble anymore folks. |
|
How long did you leave them de-registered for before you re-registered them and tried a discovery. I had to de register, leave it over night Do you have a link to setting habridge up on Mac? |
|
|
Just long enough to get them all offline. I didn't register them again until I had the bridge sorta working. |
|
I found you did have to leave them unregistered for a time. |
Thanks so i can close this issue because i'm running ha-bridge on synology docker and port 80 is reserved for synology system it's was a long time i didn't discover device |
|
Now it's completely finish with that kind of devices - indepdendently from the "virtual" link button - "ON" vs. "OFF": |
|
So after not discovering any new devices for the last two weeks i decided to try and edit the unique ids in the device.db-file: |
Hello Thanks for the release
My device still not recognize by amazon echo.
i try :
but amazon still not find any device
(i have 3 different amazon echo, echo spot, echo dot)
i use a tplink router and upnp is available.
habridge run on docker on synology
I don't find the problem.
my conf
thanks
The text was updated successfully, but these errors were encountered: