Alexa always response "this command is not compatible with this"

Eduardo Lezcano

Hi,

I have configured Alexa and Triggercmd in my raspberry pi 3, I have added some commands in the command.json configuration.
Triggercmd skill detects it correctly, but when I as Alexa to execute them, it always response "[name of the command] is not compatible with this", do you know what can be the problem? Thanks

Russ

@Eduardo-Lezcano, it sounds like Alexa isn't even invoking the TRIGGERcmd.

What are you saying to Alexa?

Did you enable the original TRIGGERcmd skill or the TRIGGERcmd Smart Home skill?

Also, do you see the sentences in the web interface under Voice commands?

Eduardo Lezcano

Hi,

I said to Alexa "Alexa open Television" for example, television is one of the commands that have to open a browser.
I have installed the second one, TRIGGERcmd Smart Home skill, because I can't find another one in Spain.
I can't see the voice sentences in the web interface.

Thanks for your response

Russ

@Eduardo-Lezcano, you won't be able to run commands via Alexa until you see your voice commands under "Comandos de voz Smart Home" in the web interface.

One reason might be that you haven't given your command a voice word. If you send me a private message with your account's email address, I can check.

Here's an example entry:

{
"trigger": "TV",
"command": "/usr/local/bin/television.sh",
"ground": "foreground",
"voice": "television"
},

If you have that on your default computer, you should be able to say, "Alexa, enciende la television."

If you have that on your non-default computer, you'll should be able to say, "Alexa,
enciende la television en laptop." (where laptop is the computer's voice field value)

Also, just to confirm, you're able to run these commands from the web interface just fine, right?

Eduardo Lezcano

I have checked with the default command.json configuration, the voice word in the default file for the foreground is "edit":
{"trigger":"Gnome Editor","command":"gedit","ground":"foreground","voice":"edit","allowParams": "false"}
But if I say " Alexa, abre edit" it still saying "edit is not compatible with this"

I have sent you my email by chat. Thanks

Eduardo Lezcano

Hi,

About the command through the web interface, when I trigger the command with the button, the order is sent to my raspberry and I can see it in the service, but nothing happens.
Thanks
BR

Russ

@Eduardo-Lezcano, let's not focus on Alexa until you can run commands via the web interface.

The service on the raspberry pi is the background service so it only runs background commands as the root user.
That's generally what people would do with a Raspberry Pi, but you apparently have X-Windows installed and want to launch a web browser in the foreground as the regular pi user.

To do that, you'll need to open a terminal Window, run the triggercmdagent command manually, and leave it running. If you ran it before as root, it will prompt you for the token again because now you're running it as pi. You'll also need to delete your computer first because you're not subscribed so you can only have one computer right now.

Leave that terminal Window running, and don't CTRL-C out of the agent. At that point you can launch X-Windows applications like firefox, but you'll need to add them to your /home/pi/.TRIGGERcmdData/commands.json file first.

I'm not sure whether the default Gnome Editor command uses the right path for where it exists on the Pi - assuming it does exist on the Pi. To get the firefox path, you can run this command: which firefox

Eduardo Lezcano

@Russ said in Alexa always response "this command is not compatible with this":

The service on the raspberry pi is the background service so it only runs background commands as the root user.

I have tried always to configure the commands as foreground because I can't see the background commands, even if I execute the installdaemon.sh file.
So I can't use the background command in my pi.
I have tried to run triggercmdagent as root or pi, and configure one computer by each one (not at the same time because I'm not subscribed as you comment) but it didn't work.
I don't know what is the problem.
Thanks

Russ

@Eduardo-Lezcano, I'm assuming you want to run commands in the foreground because your use-case is to launch a browser. I'll assume you want to run firefox, and that the path to firefox is /usr/local/firefox/firefox (I'm sure the path is different, but I don't have a Pi with X-Windows and Firefox installed).

You should be able to get it working with these steps:

Install Firefox on your Pi and test it.
Delete your computer in the web interface.
Open a terminal in X-Windows on your Pi
Say logged in as pi, don't run sudo su -
Run triggercmdagent
Enter your token
Edit your /home/pi/.TRIGGERcmdData/commands.json file
Add this entry to your commands.json file:
{"trigger":"Firefox Test","command":"/usr/local/firefox/firefox","ground":"foreground","voice":"firefox","allowParams": "false"},
Make sure the last command in your commands.json file does not have a comma at the end.
Log in at www.triggercmd.com, and click the Trigger button to run Firefox on your Pi.

If you can get that working, I'm sure we can figure out the rest.

Eduardo Lezcano

Hi Russ,

Thanks for your help again. I have followed all your steps and when I have launched the trigger a new firefox window was opened in my raspberry, so it's work.
But, the voice commands still do not appear on the website. What are the next steps from here?

BR,
Eduardo

Russ

Awesome @Eduardo-Lezcano, that's good progress.

There are two reasons the voice commands wouldn't show up on the website:

The voice field for the computer is empty. Use the Edit button on the website to fill that in.
The voice field for the command is empty. Use the commands.json to fill that in ("voice":"firefox").

Can you verify both of them have a word in them? For a Raspberry Pi I like to use the word "pie" in the computer's voice field because it's what Alexa or Google Assistant think you're saying when you say Pi.