Release Candidate and Support: Amazon Echo Control Binding

Did reboot and restart several times, but I think the error occurs when there are too many “Alexa calls” in a short period of time.
It seems to be a problem from the Amamzon server side.

Yes that can be a problem and is mentioned several times in this topic. You can move to the beta version, I think it supports multi messages just not multi TTS messages.

1 Like

Thanks for the help.
For now I disabled the logging of WARN for the binding, should do the trick for me, as everything works smooth.

1 Like

@michi

  • added stacked or grouped textToSpeech via sequences
  • added set ttsvolume in stacked or grouped announcements & textToSpeech via sequence
  • fixed update or refresh volume immediately after a command (before updated on second command and broke ttsvolume, command, volume sequence)
  • fixed update or refresh volume immediately after manual echo button press (before did not update or refresh anyway)

Regards,

Trinitus01

1 Like

Where can this update be downloaded?

Hi,

thank you very much for your interest in the update.
I would really like to publish the modified version,
but there is still no response from the initial contributor @michi.
He has to revise the code first and maybe merge the changes into the official version or else it could happen that two different versions exists.
Otherwise if he agrees I could send the modified version to designated people for testing.
Until i receive feedback from @michi we have to remain patient.

Regards,

Trinitus01

4 Likes

I too am getting Bad Request errors.
It is getting difficult to know in which thread to report such issues.

Regards
Paul

Great to see that you fixed these bad requests!

I’m almost have the same problem. I’ve 2 echo at home both of them work with TTS or startCommand but no sound at all when i try to trigger an alarm. (by rules, by paper ui control, or sitemap). I’m using 2.5.2

It is still not working, but I haven’t tried to fix it because I am using the announcement channel instead.

Hi,
i have some problems to use announcement with my echoshow. Here my thing configuration:

Thing echoshow echoKitchen "Alexa" @ "Kueche" [serialNumber="G000XXXXXXXXXXXX"]

and my item:

String Echo_Kitchen_Announcement "Announcement" (Kueche) {channel="amazonechocontrol:echo:account1:echoKitchen:announcement"}

If i call:

Echo_Kitchen_Announcement 'door opened'

nothing happends, if i change the thing from echoshow to echo:

Thing **echo** echoKitchen "Alexa" @ "Kueche" [serialNumber="G000XXXXXXXXXXXX"]

everthing works fine. Do you know this problem?

Regards
Ralph

Have you activated the announcement feature at the echoshow device via alexa app?

Yes i have activated the announcement feature.

Hi @michi I am brand new to OpenHab and have got things setup and the account is showing my devices etc. One thing I am unsure of is if and how I can send a command to alexa in general from a rule. What I am trying to do is when i start playing a movie on Plex it sends a command to Alexa to turn off the living room lights then when the movie is paused or stopped, turn on the lights. I was attempting to use the SendMessage channel on the account but nothing happens when the command fires. Is there an example of how I can achieve the above?

Question / Answer Rule?

Has anybody figured out how to TTS a question then have Alexa wait for the response from you in order to interact with your rules based on your response?

Best, Jay

Hi,
I´m using the binding for 3 echos. Is there way to find out, which echos receives the call?
I need this information to give an answer back only at this device (echo).

Thanks in advance
Benno

Look at lastVoiceCommand.

Hello H102,
perfect, thank you very much.
I don’t know how I missed it.
Works perfectly for me!

1 Like

I have some difficulties with lastVoiceCommand since yesterday. The channel does not get any updates. Re-configured the items and re-started OH made it work for an hour or so. Same problems this morning. Anyone else?

btw: i am using alexa.amazon.de, OH 2.5.4 with the respective binding version.

EDIT: not sure what’s going on. Works again after 2 reboots … let’s hope for the best

Hi All

Where can I find the available choices for the System Alerts? I want a siren like alert if theres one available

Id like to use these ones

https://developer.amazon.com/en-US/docs/alexa/custom-skills/ask-soundlibrary.html

Thanks

Further, I am constantly getting this error on the 2.4 stable, with latest snapshot as per the above post:

22:02:27.201 [WARN ] [ntrol.internal.handler.AccountHandler] - handling of websockets fails: {}
org.openhab.binding.amazonechocontrol.internal.HttpException: GET url 'https://alexa.amazon.com.au/api/activities?startTime=1588507346810&size=10&offset=1' failed: Bad Request
        at org.openhab.binding.amazonechocontrol.internal.Connection.makeRequest(Connection.java:587) ~[195:org.openhab.binding.amazonechocontrol:2.5.0.201904031156]
        at org.openhab.binding.amazonechocontrol.internal.Connection.makeRequestAndReturnString(Connection.java:445) ~[195:org.openhab.binding.amazonechocontrol:2.5.0.201904031156]
        at org.openhab.binding.amazonechocontrol.internal.Connection.makeRequestAndReturnString(Connection.java:440) ~[195:org.openhab.binding.amazonechocontrol:2.5.0.201904031156]
        at org.openhab.binding.amazonechocontrol.internal.Connection.getActivities(Connection.java:868) ~[195:org.openhab.binding.amazonechocontrol:2.5.0.201904031156]
        at org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler.handlePushActivity(AccountHandler.java:750) ~[195:org.openhab.binding.amazonechocontrol:2.5.0.201904031156]
        at org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler.handleWebsocketCommand(AccountHandler.java:695) ~[195:org.openhab.binding.amazonechocontrol:2.5.0.201904031156]
        at org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler.webSocketCommandReceived(AccountHandler.java:683) [195:org.openhab.binding.amazonechocontrol:2.5.0.201904031156]
        at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection$Listener.onWebSocketBinary(WebSocketConnection.java:406) [195:org.openhab.binding.amazonechocontrol:2.5.0.201904031156]
        at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onBinaryMessage(JettyListenerEventDriver.java:82) [92:org.eclipse.jetty.websocket.common:9.4.11.v20180605]
        at org.eclipse.jetty.websocket.common.message.SimpleBinaryMessage.messageComplete(SimpleBinaryMessage.java:68) [92:org.eclipse.jetty.websocket.common:9.4.11.v20180605]
        at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage(AbstractEventDriver.java:66) [92:org.eclipse.jetty.websocket.common:9.4.11.v20180605]
        at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onBinaryFrame(JettyListenerEventDriver.java:68) [92:org.eclipse.jetty.websocket.common:9.4.11.v20180605]
        at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:157) [92:org.eclipse.jetty.websocket.common:9.4.11.v20180605]
        at org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:476) [92:org.eclipse.jetty.websocket.common:9.4.11.v20180605]
        at org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:220) [92:org.eclipse.jetty.websocket.common:9.4.11.v20180605]
        at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:220) [92:org.eclipse.jetty.websocket.common:9.4.11.v20180605]
        at org.eclipse.jetty.websocket.common.Parser.parse(Parser.java:245) [92:org.eclipse.jetty.websocket.common:9.4.11.v20180605]
        at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:560) [92:org.eclipse.jetty.websocket.common:9.4.11.v20180605]
        at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:391) [92:org.eclipse.jetty.websocket.common:9.4.11.v20180605]
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281) [75:org.eclipse.jetty.io:9.4.11.v20180605]
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) [75:org.eclipse.jetty.io:9.4.11.v20180605]
        at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:291) [75:org.eclipse.jetty.io:9.4.11.v20180605]
        at org.eclipse.jetty.io.ssl.SslConnection$3.succeeded(SslConnection.java:151) [75:org.eclipse.jetty.io:9.4.11.v20180605]
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) [75:org.eclipse.jetty.io:9.4.11.v20180605]
        at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) [75:org.eclipse.jetty.io:9.4.11.v20180605]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) [87:org.eclipse.jetty.util:9.4.11.v20180605]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) [87:org.eclipse.jetty.util:9.4.11.v20180605]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168) [87:org.eclipse.jetty.util:9.4.11.v20180605]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126) [87:org.eclipse.jetty.util:9.4.11.v20180605]
        at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366) [87:org.eclipse.jetty.util:9.4.11.v20180605]
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762) [87:org.eclipse.jetty.util:9.4.11.v20180605]
        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680) [87:org.eclipse.jetty.util:9.4.11.v20180605]
        at java.lang.Thread.run(Thread.java:748) [?:?]