I had the same problem, and tried the same things - until I realised that as well as putting the new beta binding in addons, I needed to uninstall the binding in paperUI.
After I had done that, it went online without a login.
2018-11-08 22:09:37.914 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.amazonechocontrol.handler.EchoHandler@xxxxxxx': POST url 'https://alexa.amazon.com/api/behaviors/preview' failed: Bad Request
UPDATE: Per @michi’s follow-up tip I changed my TTS voice rules to use the new channel called “textToSpeechVolume” instead of the binding’s old “volume” channel. So far I haven’t seen the error.
And the new channel command has simplified my rules. I used to have to something like this to set the TTS volume for my voice group messages:
VolumeStates = storeStates(EchoVolumeGroup1)
if(Echo_Kitchen_Volume.state!=UNDEF && Echo_Kitchen_Volume.state!=NULL) {
Echo_Kitchen_Volume.sendCommand(60)
}
if(Echo_Office_Volume.state!=UNDEF && Echo_Office_Volume.state!=NULL) {
Echo_Office_Volume.sendCommand(60)
}
if(Echo_Theater_Volume.state!=UNDEF && Echo_Theater_Volume.state!=NULL) {
Echo_Theater_Volume.sendCommand(60)
}
EchoTTSGroup1.sendCommand('Attention! There is a problem with the Laundry Dryer.')
if (DryerCommVolTimer === null) {
DryerCommVolTimer = createTimer(now.plusSeconds(5)) [|
restoreStates(VolumeStates)
DryerCommVolTimer?.cancel()
DryerCommVolTimer = null
]
}
But now its as simple as this:
EchoVolTTSGroup1.sendCommand(60)
EchoTTSGroup1.sendCommand('Attention! There is a problem with the Laundry Dryer.')
BTW, there’s a similar volume setting channel called “notificationVolume” that allows the binding to change the alert sound level. Used together with the textToSpeechVolume command my voice alerts rules have less clutter. Thanks!
I was finally able to investigate this issue because last week I switched to OH 2.4 snapshot 20181104134837-1 along with Echo Control Binding Beta 5. I don’t see the reported problem. Hopefully the latest updates have fixed it for you.
Thanks mate. That has worked for me. Missed the uninstall from paperui. Added to addons folder. Uninstalled. Stopped, Cleaned cache, Started. Logged in to Amazon account and the world is good again.
As far as I know the only audio files you can access through this binding are those stored on the providers shown in the supported musicProviderId list found in the echo device’s control page. For the Echo Dot and Echo Show the list is only four sources:
CLOUDPLAYER
AMAZON_MUSIC
I_HEART_RADIO
TUNEIN
So you should be able to access your Amazon music from this binding if you specify the channel’s musicProviderId as AMAZON_MUSIC. But even if you get it to work I suspect it will be short term fix since Amazon is shutting down their cloud service.
I’ve failed at that, but haven’t given up.
I have a Synology NAS running the Plex Media Server. Plus I’ve installed the Plex Skill in my Amazon account. I can play the stored music files by voice command from any of my Echo devices but not from the Echo Control binding.
However, I’ve come to the conclusion that this binding won’t support Plex voice actions. But OH2 has a Plex binding (Plex - Bindings | openHAB) so I will try that next. Along with the hue emulation I think I can control the Plex server from an Echo. Or so I hope.
2018-11-14 16:35:36.175 [INFO ] [mazonechocontrol.internal.Connection] - Login failed: POST url 'https://www.amazon.com.au/ap/signin' failed: Not Found
Can anyone explain what the impact is other than a log entry every minute?
same for me in AU, I note the later versions have a fix.
I’m going to try the beta binding
ok if you are having issues just uninstall the in built binding through paperui and drop the 2.4 (6) from the first post in to the usr/share/openhab2/addon folder
2018-11-14 17:52:50.022 [INFO ] [.jetty.server.handler.ContextHandler] - Started HttpServiceContext{httpContext=DefaultHttpContext [bundle=org.openhab.binding.amazonechocontrol_2.4.0.201811110923 [263], contextID=default]}
2018-11-14 17:52:50.026 [INFO ] [internal.service.FeaturesServiceImpl] - Done.
2018-11-14 17:52:50.543 [INFO ] [mazonechocontrol.internal.Connection] - Login failed: POST url ‘https://www.amazon.co.uk/ap/signin’ failed: Not Found
If I try and browse to that , I get " Looking for Something?
We’re sorry. The Web address you entered is not a functioning page on our site." from amazons website.
When I’ve tried the activation step listed in the docs, (http://openhab:8080/amazonechocontrol/6daee338/ in my case) , it does load (after a few seconds), a page of non-text chars,which I thought looked suspicously like a compressed archive, but having just saved it out and viewed in notepad+, there’s syn and ack symbols in there, so presumably it’s the reply back from amazon, but being https it’s not legibile. (watched tcpdump on my OH2 box while hitting the amazonechocontrol link, and it has activity each time I reload the link)
Anything I can do to help debug?
Keen to get my echo dot(s) hooked up to OH2 as I’m trying to pickup workng on it after a long while with no time to play with it
thanks
I’m less worried about getting the beta installed now.
