Preview and Beta: Amazon Echo Control

[michi (Michael Geramb)]

@vzorglub

have though that the state on the item would have been updated after the 10 minutes pooling period but that doesn’t appear to be the case

This seems to be a bug in the current beta (2019-09-12)

[michi (Michael Geramb)]

@salexes

What if I have for examples two timers?

You will always see the one with the shortest time left

[michi (Michael Geramb)]

@vzorglub

However, I see no update of the items even after more than 10 minutes and I know that they have changed (ie, the temperature on the Nest is different than the item on OH or I have manually turned on a socket) I should be able to see my items updated at least every 10 minutes but I see nothing.

Sorry, this is a bug in the current beta (2019-09-12)

[michi (Michael Geramb)]

@ChrisSc

I can confirm, no announcement channel for multiroom groups with beta 2019-09-11.

The amazon API does not support the sending of announcments to multiroom groups.

[salexes]

@salexes

Also will setting a timer be implemented aswell? (I know I ask this a few times in the normal thread but I thought I could ask again in this beta thread.) If it will not be implemented could you tell me how I can use the “REST API” you mentioned in the other thread ?

Any link for guidance for me.?

[michi (Michael Geramb)]

@salexes

Any link for guidance for me.?

No really, because this is a lot of work. But I can give you some hints, you can use the development tools (e.g. F12 with Chrome) of your browser to see the http requests. Just open the page You've received an Alexa Link and you will see the call which is needed to get a list of the alarms. In this case it will be
Amazon.de
With this information you can make the same call though the proxy. Check the documentation (“Advanced Feature Technically Experienced Users”) Amazon Echo Control - Bindings | openHAB how the url must be.
So for this example it should be something like http://openhab:8080/amazonechocontrol/account1/PROXY/api/notifications
I expect you will not need the cached parameter and the number (the number is only used to prevent the browser to return a browser cached result).
Good luck!
Michael

[michi (Michael Geramb)]

New version 2.5 (2019-10-23) released.

• New configuration for polling interval in Account Thing.
  It’s now possible to configure 2 polling intervals, one for direct controlled devices and one for skill controlled devices. There is one more polling interval used with a fixed interval of 10 seconds if you use the glassBreakDetectionState or the smokeAlarmDetectionState.

• New channel ‘sendMessage’ which turns on the green light on the echo device and you can ask afterwards for the stored message.

The alexa guard features are now tested. Please note, that they not available in all amazon domains. The binding can not work around this. The second what you should now is, if you use the glassBreakDetectionState or smokeAlarmDetectionState channel, that a very fast polling with 10 seconds will be done to get the alarts because there is no active notification from the amazon server.

Download the new version from the top most posting.

Best, Michael

[PottiMc (Andre Wegmann)]

At first, thank you for your amazing Binding! Works quite well for all the functions it is offering.

I have a short question, using OH2.5 Snapshot and the latest beta of the binding. My title and imageURL field is not updating automatically. I need to press play/pause button and then it is updating by itself. Is there any chance to make an automated request or something?

[Himbeere3.1415926 (Sascha Mai)]

Hi @All.
I‘ve got the same issue with this version. Thanks for any help on this.

[michi (Michael Geramb)]

@PottiMc

My title and imageURL field is not updating automatically

@Himbeere3.1415926

I‘ve got the same issue with this version.

It seems, there was an issue at amazon site. There was also no update in the alexa app. But now, it seem, that amazon have fixed the problem.
Is the binding now working?

[Bredmich (Michael)]

I just had a message in my Alexa app that i can now allow third party skills to use the voice profiles.
Michael, could you check if the voice profile information is now listed on the Alexa websites to use it in the binding?

kind regards
Michael

[Himbeere3.1415926 (Sascha Mai)]

Yes. It’s working again. Thx

[davorf]

Hello!

Does this beta (or stable) provides queuing text-to-speech messages in any way? I’ve used it with AlexaPi (Raspberry Pi with Amazon Device SDK), and it queued sent messages, but after switching to real Echo Dot device it plays only the last message I send. I have few rules in OH that sometimes trigger in consecutive order, and they send text-to-speech to Echo - but now only the last message is being played. I’ve made some primitive queue with expire binding, but it delays messages, and it still doesn’t help if I send message from OH while Echo is playing message from some other source (timer, reminder…).

Best regards,
Davor

[Bredmich (Michael)]

Hi Davor
queuing is currently not supported but Michael already mentioned he would try to build something when there´s enough time.

kind regards
Michael

[PottiMc (Andre Wegmann)]

Yes, for me too. Thankyou!

[regissg (Régis Saint Girons)]

I am using a lot the Amazon Echo Control binding and I am very excited to test the new beta version. I have however few questions on the update procedure to make sure I am not messing up as I have never played with beta version so far:

@michi

Steps for update from previous version (If you want use the new channels):

1. Remove discovered echo devices from your inbox
2. Remove all your existing echo things (If you have created them in PaperUI)
3. Replace now the binding jar
4. Create your things to get the new channels
5. In PaperUI some channels are only shown if the “show more” (top right corner) option in the thing page is activated

The update procedure indicates that I need to replace the binding jar. Do you mean that I just need to replace the org.openhab.binding.amazonechocontrol-2.5.0.M3.jar file in the openhab\addons\bundles\org.openhab.binding.amazonechocontrol\2.5.0.M3 folder (windows 10)? Do I need to delete the org.openhab.binding.amazonechocontrol-2.5.0.M3.jar.sha1 file in that folder?

I was wondering if, after the update process you describe, PaperUI will maintain the same echo item references or if they will change randomly (I am using a bunch of Echo devices all discovered through PaperUI and I use many echo items references in my rules) ?

My interest with the beta version is to create rules for the Echo controlled Smart Home Devices (I am using a bunch of Ikea Tradfri lights controlled directly by the Echo Show zigbee gateway). One of the rule I will need is to take action when a specific light is switch on. Do I understand correctly that I will have at the minimum a latency of 10 seconds on Smart Home Devices state change even for the devices directly controlled by the Echo Show Gateway?

[michi (Michael Geramb)]

@Bredmich

I just had a message in my Alexa app that i can now allow third party skills to use the voice profiles.
Michael, could you check if the voice profile information is now listed on the Alexa websites to use it in the binding?

I enabled the option in my account, but it seems, that the notifications and the history have no hint for the user.

[michi (Michael Geramb)]

@davorf

Does this beta (or stable) provides queuing text-to-speech messages in any way?

No, and the request to the amazon server returns immediately. So the binding have no information if the text is already spoken.
My idea for the future is, that I start a short timer if the binding receives a TTS command. If I got multiple requests in this timer interval with the same text (which happens if you write to a group of alexa devices the same TTS), I sent it with the annoucment command, because this command can be sent to a list of devices. This will fix the issue with sending TTS to a lot of devices, but it will be still not a queue to speak multiple different messages one after another.

[michi (Michael Geramb)]

@regissg

The update procedure indicates that I need to replace the binding jar. Do you mean that I just need to replace the org.openhab.binding.amazonechocontrol-2.5.0.M3.jar file in the openhab\addons\bundles\org.openhab.binding.amazonechocontrol\2.5.0.M3 folder (windows 10)? Do I need to delete the org.openhab.binding.amazonechocontrol-2.5.0.M3.jar.sha1 file in that folder?

I was wondering if, after the update process you describe, PaperUI will maintain the same echo item references or if they will change randomly (I am using a bunch of Echo devices all discovered through PaperUI and I use many echo items references in my rules) ?

• Just uninstall original binding in the paperUI (This will not delete the things)
• Copy the beta JAR file to the addons folder (The location is documented here)
• If you want use new channels which wasn’t available at the previous version, you have to delete and recreate the thing

@regissg

I am using a bunch of Ikea Tradfri lights controlled directly by the Echo Show zigbee gateway

• Enable the option to discover Skill devices in the Account Thing of this beta version.

[Matt_Foreman (Matt)]

Hey guys, has anyone implemented a use for the “Send Message” feature introduced in the last beta update as listed below? I would love to see any examples of the use cases for this.

New channel ‘sendMessage’ which turns on the green light on the echo device and you can ask afterwards for the stored message.

Top Most Posting