I have restarted several times, and I did a whole re-install of openhab(ian), as well. No effect.
I added this code as a .things file.
The Echo is recognized immediately, and the channels are working flawlessly.
The EchoShow does not show up at all.
2018-03-10 11:48:45.054 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'amazon.things'
2018-03-10 11:48:45.059 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model 'amazon.things' is either empty or cannot be parsed correctly!
2018-03-10 11:48:45.087 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'amazon.things'
Maybe the format has to be different for EchoShows?
Do you have defined it in PaperUI or in a thing file?
If it is in a thing file, post the configuration without your private information. If you have defined it in paperUI, have you used the discovery feature?
You can try. Another thing what I have heard from users:
Stop openHAB
Login with a webbrowser to the Alexa website.
Close your browser
Start openHAB
The best way would be to use a webbrowser on the same machine. If this is not possible, you can try that you shutdown the computer with the openHAB and start another machine from the same IP Address. But I donât know if any of them work.
You can also try to configure the tracing for debug level, than we get a message with the amazon response, so that we can se whatâs going wrong.
@michi Thanks for your work on this great OH binding!
I was able to authenticate successfully while having using two-factor enabled on my Amazon account. I used the guidelines listed on this page to get it to work. I was concerned that it wouldnât work after a server restart but I can confirm that it is still able to connect after a full restart.
Related to the startRoutine channel, based on your description, I assumed that you could send anything that you would say to Alexa, and therefore interact with any skills, but it looks like it is only working for Alexa routines that you have setup on your account. So it looks like you are limited to what the routine functionality has to offer. Is my understanding of this channel correct?
On a side note, do you any plan on adding a channel to interact with timers? The ability to track timers and possibility create timers across other echo devices would be amazing.
Hallo jeshab,
Thank you for your investigation and this hint. But Iâam afraid, that it will fail after 5 days. I don not make a new login when open hab is restarted. I store the login cookie in the files system under the user data folder. After 5 days, I have to do the login again to refresh the cookie. Do you know if the additional code will be required for every login? Or only the first time? Please let me know if the binding still works after five days. (You can check if the new login was done by looking in the amazonechocontrol subfolder under userdata. There is an text file for the account device with a timestamp)
No I can only trigger the preview function of routines.
The binding is now also available from the openHAB marketplace integration!
IF YOU HAVE PREVIOUSLY INSTALLED THE BINDING MANUAL, remove first the binding from the AddOn directory and reboot openHAB. (WARNING: I currently not know what happens with things defined in PaperUI, things defined in files appear again after the binding installation)
Configure the markplace in openHAB to âMaturity Levelâ Alpha or Beta and switch on the âInclude Bindingsâ flags to see the binding.
Michael,
I followed your directions to use the marketplace binding. Everything worked great. Do you know how I would list that in my addons.cfg file to get it to automatically load after a reboot?
Thanks for the clarification. So I removed the properties file with the cookie information and as you expected, it is no longer able to connect. Moreover, because it keeps on trying after that failure, I wasnât able to get it to work using the guidelines.
This was because the Amazon captcha showed up after the binding failed to login after a number of times. An easy way to confirm/clear it is to open a private browser session and try to log in into that account and enter the captcha code. Once I did this, the binding was able to log in again using the same authentication guidelines.
So as long as the cookie is being used, we should be fine. Is there a reason for refreshing it every 5 days especially if the session is still valid? To compare to a browser experience, I donât think Amazon re-prompts for a password authentication after the initial login and I would assume the browser uses the cookie session information for quite a while.