Release Candidate and Support: Amazon Echo Control Binding

Hi Michi,

Thank you. i got RC2 version of jar file. seems RC2 file size has increased compared to RC1

Kind regards

I just downloaded the latest version (link from the top of this thread) and use OH 2.2 stable.

I can add to the inbox manually the Amazon Account, but it keeps the status uninitialized.

I double checked the password, but got an error 500 when creating the thing the first time and then conflict, when I try to save it again.

I don’t use 2 factor authentication.

Is there an issue with a German OH2 ?
Any suggestion is greatly appreciated

Just recognized that there was another file for download added an hour ago.
This seems to work so far… :slight_smile:

Important for all Beta and Release Candidate users with flashbriefingprofiles:

If you use flashbriefingprofile with saved configuration, please install the RC3, otherwise the stored profile configuration get lost after upgrade to the next version. If you don’t use flashbriefingprofiles, there is no need to upgrade.

RC3 is available in openHAB marketplace or as download if you use OpenHAB 2.2:

For the daily snapshot 2.3 build of openHAB use this version:

if you open the page http(s)://youropenhab:port/amazonechocontrol (e.g. http://localhost:8080/amazonechocontrol) you can verify if the RC3 is correctly installed. it should look like that:

Seems not working for me.
I had uncomment line. Run the script. But nothing happened.

How I can ensure that scapy is working correctly?

To update the binding, do we need to remove all items and things, replace the binding and re-add things and items?

FAQ: When I have to remove and recreate things for a binding upgrade?

a) If you have defined the things in a thing file

b) If you have defined the things in PaperUI
If the newer version of the binding has new channels, which you want use: Remove the thing and recreate them after the update.
If you don’t need the new channels, you have nothing to do!

This behavior is not related to the binding, it’s a issue of OpenHAB. So this rules are valid for all bindings!

Whats does this means:
For update from RC1, RC2 to RC3 -> Definitely no action required, because there are no new channels

From previous beta versions, check the documentation, please note there are breaking changes between the Beta and the RC version, which means some old channels will no longer work! You will find the necessary steps in the top most posting.

1 Like

Can confirm, removed the previous jar file, replaced it with RC3, done.

Hi to all.
I don’t know if someone have the same problem.
I change the volume of Alexa in the night to a lower level. Before i check the volume level. Is it not the level I want -> change or not.
Since today the rule doesn’t work correctly. Because the state of volume channel is undef. After openhab changed the volume, the item goes back to undef.

Hi @Balaganov,

first of all it is important that the script is running on a machine where the traffic goes through. I have a central server instance that acts as a router, firewall and host for other virtual servers. All Internet traffic needs to go through the instance where the script is located.

You should see traffic when you uncomment the 

line and change the following line like

sniff(prn=pack_received, iface="YOURINTERFACE", store=0, count=0)

This does not apply any filter and should show you a lot of packets. If this works, everything should be ok with your setup.

Dear Beta tests,

I’am happy to announce:

The “Amazon Echo Control” binding will be part of the official OpenHAB 2.3 distribution

Starting from the build tonight, the binding is include in the daily snapshot (unstable) build of OpenHAB 2.3. Please read this post and this post before you upgrade.

I want to say thank all of you for your beta testing. Thanks for you patience and endurance to bring the binding to this level!


That is awesome - great work!!

thanks for the effort you’ve put into this binding!

“if you open the page http(s)://youropenhab:port/amazonechocontrol (e.g. http://localhost:8080/amazonechocontrol 7) you can verify if the RC3 is correctly installed. it should look like that:”

I dont have this URL? page not found

For anyone interested in the alarm sounds - here is my list out of the REST interface (I assume everyone has the same list?

        "value": "ECHO:system_alerts_soothing_01",
        "label": "Adrift"
        "value": "ECHO:system_alerts_atonal_02",
        "label": "Clangy"
        "value": "ECHO:system_alerts_melodic_05",
        "label": "Clarity"
        "value": "ECHO:system_alerts_repetitive_04",
        "label": "Countertop"
        "value": "ECHO:system_alerts_melodic_03",
        "label": "Focus"
        "value": "ECHO:system_alerts_melodic_06",
        "label": "Glimmer"
        "value": "ECHO:system_alerts_repetitive_01",
        "label": "Nightstand"
        "value": "ECHO:system_alerts_melodic_07",
        "label": "Nimble"
        "value": "ECHO:system_alerts_soothing_05",
        "label": "Orcas"
        "value": "ECHO:system_alerts_atonal_03",
        "label": "Porchlight"
        "value": "ECHO:system_alerts_rhythmic_02",
        "label": "Pulsar"
        "value": "ECHO:system_alerts_musical_02",
        "label": "Rainier"
        "value": "ECHO:system_alerts_melodic_01",
        "label": "Simple Alarm"
        "value": "ECHO:system_alerts_melodic_02",
        "label": "Simple Timer"
        "value": "ECHO:system_alerts_alarming_03",
        "label": "Squared Waves"

I am using a rule to set a volume before an announcement. A few seconds after I send the new volume command I see th Alexa go from the volume I set to either undefined or 2% higher than the value I sent.

edit to add… Alexa volume voice command is integer steps 1 to 10. I suspect that the unstable volume may be happening when % values are used that fall between the equivalent integer eg 30 is OK but 35 jumps around

Hey @michi,
any idea what causes this error :

2018-05-29 19:33:33.869 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.amazonechocontrol.handler.EchoHandler@b60de0': POST url '' failed: Not Found

org.openhab.binding.amazonechocontrol.internal.HttpException: POST url '' failed: Not Found

	at org.openhab.binding.amazonechocontrol.internal.Connection.makeRequest( [216:org.openhab.binding.amazonechocontrol:2.3.0]

	at org.openhab.binding.amazonechocontrol.internal.Connection.command( [216:org.openhab.binding.amazonechocontrol:2.3.0]

	at org.openhab.binding.amazonechocontrol.internal.Connection.playRadio( [216:org.openhab.binding.amazonechocontrol:2.3.0]

	at org.openhab.binding.amazonechocontrol.handler.EchoHandler.handleCommand( [216:org.openhab.binding.amazonechocontrol:2.3.0]

	at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source) ~[?:?]

	at sun.reflect.DelegatingMethodAccessorImpl.invoke( ~[?:?]

	at java.lang.reflect.Method.invoke( ~[?:?]

	at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect( [101:org.eclipse.smarthome.core:0.10.0.oh230]

	at org.eclipse.smarthome.core.internal.common.InvocationHandlerSync.invoke( [101:org.eclipse.smarthome.core:0.10.0.oh230]

	at com.sun.proxy.$Proxy129.handleCommand(Unknown Source) [216:org.openhab.binding.amazonechocontrol:2.3.0]

	at org.eclipse.smarthome.core.thing.internal.profiles.ProfileCallbackImpl.handleCommand( [108:org.eclipse.smarthome.core.thing:0.10.0.oh230]

	at org.eclipse.smarthome.core.thing.internal.profiles.SystemDefaultProfile.onCommandFromItem( [108:org.eclipse.smarthome.core.thing:0.10.0.oh230]

	at sun.reflect.GeneratedMethodAccessor137.invoke(Unknown Source) ~[?:?]

	at sun.reflect.DelegatingMethodAccessorImpl.invoke( ~[?:?]

	at java.lang.reflect.Method.invoke( ~[?:?]

	at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect( [101:org.eclipse.smarthome.core:0.10.0.oh230]

	at [101:org.eclipse.smarthome.core:0.10.0.oh230]

	at [?:?]

	at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:?]

	at java.util.concurrent.ThreadPoolExecutor$ [?:?]

	at [?:?]

Hi Ben,
this means that the amazon server answer with an not found http error. I hope its an temporary problem.
Kind Regards,

1 Like

:grinning::grinning::grinning::grinning::grinning::grinning::grinning::grinning: Release Time :grinning::grinning::grinning::grinning::grinning::grinning::grinning::grinning:

OpenHAB 2.3 is released now with the Amazon Echo Control Binding



doesn’t beep for me - although the rings light up.
Either way though, this is a game changer


after my update to 2.3 stable, I wanted to use the Eche Control Binding, starting with Volume Control via KNX.
I used the KNX switch to control the volume of my Onkyo, but I want to change that to control the volume of my Echo dot.
I made a dimmer Item with a KNX Group adress and linked that to the volume thing in the Paper UI.
What happens is, that the volume is always set to 1. I think this is due to the fact, that the bus sends a 12,5% increase command again and again as long as I am on the button.

Is ther any workaround, maybe with pressing the button just once to increase the volume by one step (no press and hold)

I hope you guys understand what I mean an can give me a hint.