204 │ Active │ 80 │ 2.5.8.202007261149 │ openHAB Add-ons :: Bundles :: Amazon Echo Control Binding
I defined my thing like that.
Bridge amazonechocontrol:account:account1 “Amazon Account” @ “Accounts”
/{
Thing echo echo1 “Alexa” @ “Arbeitszimmer Michi” [serialNumber=""]
}
When I go to the page http://192.168.xx.xx:xxxx/amazonechocontrol/account1 and enter my data, I always get the message
“There was a problem, Enter a valid email or mobile number”.
My data are correct. I use a 2-factor login on Amazon.
In the Karaf Console, I log the binding in debug mode. I see these entries and some more.
Retry call to_https://api.amazon.com/auth/token
Make request to_https://api.amazon.com/auth/token
I can’t post everything because some data are sensitive.
I experimented a bit with the Smart Home Device discovery feature in version 2.5.7 and in the entry for the Echo Guard (which is not yet available in this country (Germany)) is a channel for the temperature of the Echo Plus Gen 2, but it only provides integers and no decimal values
204 │ Active │ 80 │ 2.5.8.202007261149 │ openHAB Add-ons :: Bundles :: Amazon Echo Control Binding
I defined my thing like that.
Bridge amazonechocontrol:account:account1 “Amazon Account” @ “Accounts”
/{
Thing echo echo1 “Alexa” @ “Arbeitszimmer Michi” [serialNumber=""]
}
When I go to the page http://192.168.xx.xx:xxxx/amazonechocontrol/account1 and enter my data, I always get the message
“There was a problem, Enter a valid email or mobile number”.
My data are correct. I use a 2-factor login on Amazon.
In the Karaf Console, I log the binding in debug mode. I see these entries and some more.
Retry call to_https://api.amazon.com/auth/token
Make request to_https://api.amazon.com/auth/token
I can’t post everything because some data are sensitive.
I’ve had the same problem these days. It turned out that I had loaded an older version of the binding (younger than 2.5.7) and it does not yet use the updated version of the Amazon API’s login procedure.
I have fixed the problem by
switched off the two factor authentication
uninstalled the old binding and updated it to 2.5.7
changed the Thing ID so that the cache and all associated new caches were created internally
after that i could log in normally again and after the login i activated the 2 factor authentication again.
Thank you foe the answer.
Unfortunately, that was not the solution.
Sometimes I get linked to a password reset page by Amazon.
Does anyone have an idea how I can trace this error.
Is anyone here having trouble with the StartRoutine function of the Echo Control Binding failing with a “Too many requests” error?
I posted a new topic about this in the main part of this forum here
but then discovered this thread which is probably more appropriate. Apologies for double posting, but this problem is really frustrating as I can’t figure out if it’s an OpenHAB issue, an Amazon issue, or a bit of both.
Keen to hear if anyone else has encountered this, and better still worked out how to fix it. My system used to work perfectly.
I am having the amazon sign in problem. I am using Amazon Echo Control Binding 2.5.6. I would like to update to 2.5.7 but I do not know where to find the related jar file. Could any one give me a link to it?
Thanks, I have been able to update to 2.5.7 but I keep having the amazon sign in problem. Basically (with 2.5.6 or 2.5.7) I could not complete the openhab:8080/amazonechocontrol task as Amazon Alexa keeps asking me to sign-in.
Hi! I don’t know if here is the right place for my problem, but since Version 2.5.7 I can’t use PaperUI and HABPanel. After a long research, I found out, that the problem is since Version 2.5.7. if I do a downgrade to the latest 2.5.6 Snapshot everything works fine.
The Problem is, that in PaperUI I get an ERROR 500 - Internal Server Error when I click on the control Button, or on the Item list. In the REST UI I can’t get the item list, too. And HABPanel, brings up an error, that there is no connection to habpanel. If I downgrade or even uninstall the amazonechocontroll add-on, everything works fine.
In the logs there is nothing to find and it took me weeks to find out, that the binding is the problem. I am using the docker Version, and so I have a good test environment to play around. My production openhab is still on openhab Version 2.5.6. My Test Stage is on the lates 2.5.8 docker image.
Hope someone could give me some hints, how I can solve that problem. What I did so far:
uninstalled the binding
cache clearing
Update and downgrade to snapshot versions 2.5.6 - 2.5.9
check the log files
restart the container
tried other openhab versions
uninstallation via bundle: command
up and down grade via bundle: command
delete all things and items
delete the amazon account thing
logged out the amazon account
So perhaps I missed something and someone could help me out with that problem.
I have the same problem. Every time I call alexa for some action which is not used for openhab (e.g. playing a radio station) I get a warning in the log:
2020-09-16 12:57:22.764 [WARN ] [trol.internal.handler.AccountHandler] - handling of websockets fails
org.openhab.binding.amazonechocontrol.internal.HttpException: GET url 'https://alexa.amazon.de/api/activities?startTime=1600253842371&size=10&offset=1' failed: Bad Request
This is a Parsing json failed error.
It seems that amazon API return now a version with a “x:y” format (“4:880679411” in my case), and the addon cannot parse ton number.
Am i alone ?
Thanks
No, you are not alone - same here since today:
[mazonechocontrol.internal.Connection] - Parsing json failed
com.google.gson.JsonSyntaxException: java.lang.NumberFormatException: For input string:
Some of my rules don’t work anymore since today. E.g. some calls of amazon playlists or an information about values:
[rthome.model.script.actions.BusEvent] - Cannot convert ‘here is my text (41) degrees celsius (43) percent humidity’ to a command type which item ‘Echo_room1_TTS_Volume’ accepts: [PercentType, OnOffType, IncreaseDecreaseType, RefreshType].
Seems amazon is changing something in the background, right?