Release Candidate and Support: Amazon Echo Control Binding

[michi (Michael Geramb)]

@aymeric106

If I update my openhab to latest 2.4 snapshot, will your beta be included ?

No, the beta is not included in the snapshot-build.

[michi (Michael Geramb)]

@jwiseman

hese new errors in the logs every time the device speaks.

Did you mean the TTS channel? What text have you provided? Can you test the “startCommand” channel with the String “Weather”, because this use the same technical base.

[michi (Michael Geramb)]

@tinkernut

//ALexa Open Livingroom Blinds ON
rule “Livingroom Blinds Open”
when
Item livingroom_blinds changed to ON
then
Echo_Living_Room_StartCommand.sendCommand(‘Turn ON the Livingroom Shades’)

end

The “startCommand” channel only supports the listed commands in the documentation (e.g. “Wheater”). No free text can be provided.
The only way to switch smarthome devices is using Alexa routines. These can be called from the binding with the “startRoutine”.

[ThomasOH (Thomas)]

Your monitoring script has been working great but after updating the binding to 2.4 Beta 1; I’m getting this error now for the script. The script still works though… Any updates to this script to handle this exception? {snip}

@jwiseman,

I’m not using the latest echo control binding so I haven’t encountered that problem with the Amazon Online Status email rule. So for now I don’t have a revised rule to resolve the new issue. Perhaps you or another user can debug the rule and post a fix.

• Thomas

[jwiseman (Mr. Wiseman (OH 4.2 Snapshot on Pi4))]

Yes, the TTS is what I use . . . here’s example of one of my scripts. Still works . . .

rule “Jays Home”
when
Item JsAndriodUnifi changed from OFF to ON
then
var Number hour = now.getHourOfDay
if (hour >= 8 && hour <= 21 && Home_Away.state == ON && InternetConnection.state == ON) {

		// Echo talks

		if (Echo_Basement_Volume.state!=UNDEF && Echo_Basement_Volume.state!=NULL) {
    		Echo_Basement_Volume.sendCommand('70')
			Thread::sleep(2000)  // 2 second wait
    		Echo_Basement_TTS.sendCommand("  Excuse me folks, I detect Jay's phone, so he must be home now.")
			Thread::sleep(2000)  // 2 second wait
		}
		if (Echo_Loft_Volume.state!=UNDEF && Echo_Loft_Volume.state!=NULL) {
    		Echo_Loft_Volume.sendCommand('70')
			Thread::sleep(2000)  // 2 second wait
    		Echo_Loft_TTS.sendCommand("  Excuse me folks, I detect Jay's phone, so he must be home now.")
			Thread::sleep(2000)  // 2 second wait
		}
		if (Echo_Living_Room_Volume.state!=UNDEF && Echo_Living_Room_Volume.state!=NULL) {
    		Echo_Living_Room_Volume.sendCommand('50')
			Thread::sleep(2000)  // 2 second wait
    		Echo_Living_Room_TTS.sendCommand("  Excuse me folks, I detect Jay's phone, so he must be home now.")
			Thread::sleep(2000)  // 2 second wait
		}
		if (Echo_Garage_Volume.state!=UNDEF && Echo_Garage_Volume.state!=NULL) {
    		Echo_Garage_Volume.sendCommand('70')
			Thread::sleep(2000)  // 2 second wait
			Echo_Garage_TTS.sendCommand("  Welcome Home Jay, we've missed you.")
			Thread::sleep(2000)  // 2 second wait
		}
	hour = null
	}

end

Best, Jay

[tinkernut (George)]

Ok thank you. I was able to get it to work using routines as you suggested. Thanks

[michi (Michael Geramb)]

@jwiseman

here’s example of one of my scripts. Still works . .

Hi Mr. Wiseman,
I don’t have an idea for this problem. But maybe you will test my new beta version.
Regards,
Michael

[jwiseman (Mr. Wiseman (OH 4.2 Snapshot on Pi4))]

Hi Michael,

Running your latest beta 2 on OH2.3 Synology; I’m getting this error with a clean reboot (clean cache and tmp directories). I did it twice just in case it was a one off . . .

at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [?:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [9:org.apache.felix.fileinstall:3.6.4]

2018-08-25 17:32:14.931 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/volume1/homes/openhab/addons/org.openhab.binding.amazonechocontrol_2.4.0.201808260018.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.amazonechocontrol [193]
Unresolved requirement: Import-Package: org.eclipse.jdt.annotation; resolution:=“optional”
Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.api.annotations; version=“9.3.22”

Best, Jay

[michi (Michael Geramb)]

New Beta Version 2.4. (2)

I have created a new beta version with new features.

There is now a Web-Socket connection to the amazon server, so there is no polling anymore (The option for the polling interval is not yet removed, but the setting is ignored).
Please test if the channels are updated anyway correctly.

The second new feature is the new channel “lastVoiceCommand”. This can be used to write your own handle for a voice command. Just create an Alexa routine with do nothing for the command. Then create a rule triggered by the lastVoiceCommand channel and to your own handling.

You can download the new binding from the top most posting

There is currently no better solution for the login problems which have some users. I hope I can provide a better way in any of the future version.

Regards,
Michael

[michi (Michael Geramb)]

@jwiseman

Unresolved requirement: Import-Package: org.eclipse.jdt.annotation; resolution:=“optional”
Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.api.annotations; version=“9.3.22”

Please download it again, maybe I found the problem. I have changed the link.

[Master79 (Markus S.)]

Hi.
Has someone found a solution to check how long the TTS command will be played.
If i start a second one behind, i have to use timer. But this is no nice solution.
Greetings,
Markus

[illnesse]

@michi

lastVoiceCommand

lastVoiceCommand
…

lastVoiceCommand
…

This is going to take this whole Alexa interaction thing on a whole new level, i’m on it!

[Saracen (Tom)]

@michi

The second new feature is the new channel “lastVoiceCommand”. This can be used to write your own handle for a voice command. Just create an Alexa routine with do nothing for the command. Then create a rule triggered by the lastVoiceCommand channel and to your own handling.

I’m not sure I understand the benefits of this over simply triggering an openHAB action after a Routine voice command.
Could someone give an example of a scenario where this could be used?

[illnesse]

*any voice command

[michi (Michael Geramb)]

@Saracen

Could someone give an example of a scenario where this could be used?

E.g. you can switch different items with the same voice command depending of the room (echo device)

[kugelsicha (@HerzScheisse ~ Holger)]

@michi

The second new feature is the new channel “lastVoiceCommand”. This can be used to write your own handle for a voice command. Just create an Alexa routine with do nothing for the command. Then create a rule triggered by the lastVoiceCommand channel and to your own handling.

wow this sounds great… going to play with this a bit… thanks for this feature…

and i want to ask if another thing is possible to implement…
on the echo devices we have the hardware button for mute the echo (red led ring is active)
Is there any way to active this over the binding?

My activation word is “Computer” and if I watch some movies, docus … it often happens that Alexa is anoying me… so for maximum laziness… i dont want to leave the couch to mute the device…

@michi do you think this is possible? Dont know if amazon is allowing the use of this button on software side…

[illnesse]

i’m not sure yet if i seriously want to go that way, see voicecommands.js

voice commands via alexa lastVoiceCommand, cleaned up related mqtt & echo stuff, etc

it just sucks that alexa is always responding with “can’t do this, can’t do that” even though my openhab script successfully parsed the command. Maybe i’ll just mute Alexa for everything but TTS, because honestly, all the built in features are kind of lame anyways. Maybe i can cover most of it with a routine, or i’ll add a voice command to turn on/off “TTS Only”

[illnesse]

@kugelsicha
muting won’t work until Amazon decides to add that feature to the website/app

[kugelsicha (@HerzScheisse ~ Holger)]

@illnesse

muting won’t work until Amazon decides to add that feature to the website/app

okay… thanks…

so i will try a solution with adding Alexa to a (zwave) wallplug… to shut her down… maybe with a rule with timer in it to bring her up after a couple of minutes…

[jwiseman (Mr. Wiseman (OH 4.2 Snapshot on Pi4))]

Hi Michael,

Same thing . . . Here’s the file I used for the 2nd download this morning --> org.openhab.binding.amazonechocontrol_2.4.0.201808260052.jar

2018-08-26 08:31:15.139 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/volume1/homes/openhab/addons/org.openhab.binding.amazonechocontrol_2.4.0.201808260052.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.amazonechocontrol [187]
Unresolved requirement: Import-Package: org.eclipse.jdt.annotation; resolution:=“optional”
Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.client

at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [?:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [9:org.apache.felix.fileinstall:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [9:org.apache.felix.fileinstall:3.6.4]

2018-08-26 08:31:15.188 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/volume1/homes/openhab/addons/org.openhab.binding.amazonechocontrol_2.4.0.201808260052.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.amazonechocontrol [187]
Unresolved requirement: Import-Package: org.eclipse.jdt.annotation; resolution:=“optional”
Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.client

Best, Jay