[SOLVED] Login problems when setting up Echo Control binding

Please bear with me, if this questions has already been asked somewhere. I’ve searched for a while, but did not find something.

I’ve tried to set up the Amazon Echo Control binding as described in the docs, but when doing this step

open the url YOUR_OPENHAB/amazonechocontrol in your browser (e.g. http://openhab:8080/amazonechocontrol/), click the link for your account thing and try to login

After hitting the link on that page, I get a page full of hieroglyphs, and the Thing stays offline. Here’s an excerpt to give you an idea of what I mean when I say hieroglyphs:

��Yms۸��_!q: YҴ�\�&�M^��z���$�a��A�bķ��l������ڹ�3���b��]�>K�F��t䢾-�x]�ɋS���W3�Q�}����ηb��4��D���h���<�Ͽ��H�,��J/F���Z����e\�cΞ��>��w\S����r��W���������� ��iy�ǚ�J]�Y�_����1e�� 

What version of the Alexa binding are you using?

It’s advised to not use PaperUI to install but rather install by placing the jar file in your addons.

EDIT: See below for link to jar file.

If you have installed via PaperUI please uninstall before placing the jar file in addons.

This is what I see in the log:

2018-12-16 15:46:36.711 [thome.event.ExtensionEvent] - Extension 'binding-amazonechocontrol' has been installed.
2018-12-16 16:04:18.511 [hingStatusInfoChangedEvent] - 'amazonechocontrol:account:9023c998' changed from UNINITIALIZED to INITIALIZING
2018-12-16 16:04:18.558 [hingStatusInfoChangedEvent] - 'amazonechocontrol:account:9023c998' changed from INITIALIZING to OFFLINE (CONFIGURATION_PENDING): Wait for login
2018-12-16 16:04:19.555 [INFO ] [mazonechocontrol.internal.Connection] - Login failed: POST url 'https://www.amazon.de/ap/signin' failed: Not Found
2018-12-16 16:05:20.218 [INFO ] [mazonechocontrol.internal.Connection] - Login failed: POST url 'https://www.amazon.de/ap/signin' failed: Not Found
2018-12-16 16:06:20.974 [INFO ] [mazonechocontrol.internal.Connection] - Login failed: POST url 'https://www.amazon.de/ap/signin' failed: Not Found
2018-12-16 16:07:21.676 [INFO ] [mazonechocontrol.internal.Connection] - Login failed: POST url 'https://www.amazon.de/ap/signin' failed: Not Found
2018-12-16 16:08:22.008 [INFO ] [mazonechocontrol.internal.Connection] - Login failed: POST url 'https://www.amazon.de/ap/signin' failed: Not Found
 (many times)

2018-12-16 17:29:51.477 [hingStatusInfoChangedEvent] - 'amazonechocontrol:account:9023c998' changed from OFFLINE (CONFIGURATION_PENDING): Wait for login to UNINITIALIZED
2018-12-16 17:29:51.520 [hingStatusInfoChangedEvent] - 'amazonechocontrol:account:9023c998' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)

@H102: I’ve uninstalled it from PaperUi and dropped the jar in the openhab2-addons share, but the binding does not seem to be started. It’s not even mentioned in the log, as if it wasn’t found at all. In Karaf, it does not appear on the list. What could I be doing wrong?

I’m on openHAB 2.3.0, by the way. Should the jar your provided work on that version at all?

Not sure why it’s not showing.:thinking: You shouldn’t need to restart OH but it may be worth the time to clean the cache, maybe something from the old binding is still lingering around.

sudo systemctl stop openhab2

sudo openhab-cli clean-cache

sudo systemctl start openhab2

It worked for me on OH 2.3 but I have since upgraded to 2.4.

There may be an issue with the region as I am in the U.S. ?

sudo systemctl stop openhab2

sudo openhab-cli clean-cache

sudo systemctl start openhab2

I’ve tried that, but unfortunately, it did not make a difference.

There may be an issue with the region as I am in the U.S. ?

Hm. How could that be? I’d understand if it did not work for that reason, but not why it shouldn’t be started at least?!

@H102: I’ve finally realized that the dropbox link you gave me does not download a jar, but an HTML document. So no wonder it wasn’t accepted! :slight_smile:

Is there an official way to get a binding’s snapshot? I mean, besides downloading the full openhab snapshot and extracting it from there?

As far as I know this link is the only place to get the latest and its the same dropbox jar.

Okay, the link in your quote has worked now. For some reason, your first link is broken.

Thanks!

@metin I removed the link above, hopefully no one gets confused.

Please click the post that provided the solution and edit the topic to add [Solved].

Thanks

@H102, will do as soon as I have been able to verify that the new version solves my actual problem. Haven’t had the time to test that yet.

It works perfectly now, and it’s really amazing what can be done with this binding. I’ve just totally amazed my daughter when Alexa started talking to her. :smile:

The 2.3.0 binding obviously comes with an outdated Amazon login url. It may make sense to make the url configurable?