Amazon Echo Control - TextCommand no longer work as expected

Since 28.09.2022 the “TextCommand” (execute a text command like a spoken text) of Amazon Echo Control Binding no longer work as expected - the behavior has changed. I use Openhabian 3.3.0 on a PI4. I’m not sure if this is a problem of the Echo Control Binding or a problem of the Alexa API. The VoiceCommand directly spoken to the echo device still works only the TextCommand (via API) no longer works. It seems that the problem arise in combination with Alexa skills where the first part of the TextCommand opens the skill and the second part of the TextCommand should be “transferred” to the skill. Does anybody experience the same problem … and possibly has found a solution?

example 1:
I use Echo Show 15 as Openhab dashboard and as display for the door camera. For that purpose I use the Alexa skill “MyPage”
To show the Openhab dashboard on the Echo Show, Openhab sends the TextCommand ”open My Page and load page 1” (Openhab repeat that every 6 Minutes because after several minutes of inactivity the echo show shows the default page again). When the doorbell rings, the item doorbell changes from OFF to ON and a Openhab rule sends the TextCommand ”open My Page and load page 2" to the Echo Show to show the Openhab page with the door camera view (stream) and “open door button” on the Echo Show. After two minutes Openhab sends the TextCommand ”open My Page and load page 1” to show the Openhab dashboard again. The TextCommand without "Alexa, " at the beginning.

In the above example the first part of the TextCommand “open MyPage” works but I have to write "MyPage instead of “My Page” (without space in-between). I the past it was vice versa. The second part of the TextCommand “and load page …” is wrongly understood by the Alexa API / Echo device as the Echo device responds “can’t find the video”. As said before the same command directly spoken to the echo device (VoiceCommand) still works. I have tested in English and German “öffne My Page und lade Seite …”.

example 2 (only tested in German):
VoiceCommand „Alexa, frage Miele, was meine Geräte machen“ still works but TextCommand „frage Miele, was meine Geräte machen“ does not work. The TextCommand „frage Miele" or “öffne Miele” still works (responds with introduction of the skill)

A few weeks ago I had a similar problem with the “playMusicVoiceCommand” (voice command as text. e.g. ‘Yesterday from the Beatles’) of the Echo Control Binding. The “playMusicVoiceCommand” has no longer be interpreted correctly by the Alexa API / echo device. I solved this problem (work around) by changing my Openhab rules from “playMusicVoiceCommand” to “TextCommand” … but TextCommand is now wrongly interpreted by the Alexa API too :frowning:

It would be great if anybody could help to solve this issue.

I would assume that @J-N-K s post

also is valid in this case.

1 Like

I cannot help to solve this issue, but I can confirm this strange behaviors in general.

Some times the TextCommands work. And sometimes they don’t.
And the stangest part is, that the same Voice Command works and is recognizes exactly as the written TextCOmmand.

For example Schalte TuneIn 1LIVE Wohnzimmer ein worked as a TextCommand well for month (most of the time).
But the last few days Alexa just plays some music vom Amazon Prime Music.

1 Like

I just hab another similar issue.

The TextCommand Soundbar Ton aus has worked for a few days.
But now Alexa asked “Did you mean Bedroom?”.

When I say the same words it works.

Then I noticed the recognized VoiceCommand has lower case letters.

When I change that in my rules it works.

That means:

Soundbar Ton aus ≠ soundbar ton aus


I think to remember that I had a alex routine which was working for sometime and then I also needed to change the case of a subset of the letters.


Thank you @Wolfgang_S and @christoph_wempe for your quick reply. The LowerCase approach for TextCommand solved the problem or is at least a good workaround. Everything seems to work again with that fix.


I have the same problem.
I am changing my rule now. What a strange issue :slight_smile:
Thanks for you hints!