@Russ Thank u Ross.

@nstefi, I recommend you try the Smart Home Alexa skill - it recognizes your words much better than the original skill.

That said, what exactly are you saying to Alexa? I just said these and they both worked for me:

Alexa, ask TRIGGERcmd to run calculator. Alexa, ask TRIGGERcmd to run calculator on downstairs.

@Russ thanks!

@Russ got it to work (spaces need %20 in names for anyone looking this up in the future).

Thanks a million. So cool to use commands on my fossil

Thats delightfuly simple Ill just toss that in my xboxvol script Thanks

Its back up now! Cool!

@drhoops21, that's correct - you can log into your account using your Twitter, Facebook, or Google acount as long as it's the same email address.

I don't know why your password stops working. It should never expire. Is it possible someone else is logging into your account and changing it?

Also, one thing you should know - the TRIGGERcmd forum account is separate from your TRIGGERcmd account you use to trigger your commands.

Thanks! Everything is running correctly now

@Henry-Lightfoot, I found this page that shows step-by-step screenshots. Paypal put subscriptions under "pre-approved payments."

@Dave-Johnson, that's correct - the Smart Home version does a better job of matching what you say with your commands because Amazon has a list of your commands ahead of time, but unfortunately it can't support that Voice Reply feature.

@Kent-Scherler, that can happen if you set your command to "background" but you're not running the background agent. Please please try switching it to foreground if that's the case. When you click the play button in the agent, it runs the command in the foreground.

535ee528-5761-4cb9-b707-048ba78847d8-image.png

If that doesn't work, please paste your command here. Maybe I'll see the problem.

Ah. "ping -n 6 localhost < nul" works.

Thanks for your quick response, now it works fine

@julianbr, nice job. I'm glad you got it figured out.

I was facing the same problem, but solved while writing this:

If I use the old skill and say "ask trigger CMD to run terço" it works perfect, also works from pressing "trigger" in the website.
If I use the new skill and say "turn on terço" it doesn't.

What have I tried:

Disabling and enabling the skills. Deleting and adding the command again. Removing and discovering the comands again in Alexa. Removing and re-installing the triggercmdagent. Changing voice command.

Useful info:

Only happens to that command, all the other works fine. This command is a bash script that open a few chrome pages depending on week day. I'm using Linux (PopOS 20.04). I'm using it in portuguese.

Then I decide to try changing the Trigger name. I used "batata" (potato in portuguese) and it worked, then I tried "Terço" again and it didn't, then I tried "Terco", it worked. Apparently it is a problem with "ç" in the trigger name (in the voice command is working well). Since english don't have that, it's understandable. It's not a big thing or really a problem, just wanted to inform so if anyone is having the same problem, try that.

@juanmik, it depends on the program. Some programs have their own volume but most don't.

@straximus, which Google Assistant action are you using? The Smart Home version or the original version?

@Russ I did try that before, when it wasn't working. I even deleted and recreated the routine multiple times trying to get it to work, but it just wouldn't. Not sure what fixed it but I'm glad it works now.

Amazing job, thank you again.

@Drache22, if you're using the Smart Home version of the TRIGGERcmd Alexa skill, your commands are like Smart Home switches that you're turning on or off.

If you enable parameters, make your voice word PC, and put your shutdown command in the "Off Command" field, then you can say, "Alexa, desligar PC."

318795e5-e604-45fb-8dec-eb9c2fdf83f7-image.png

If you use the non-Smart Home skill, you could keep your voice field as "desligar pc" and say: "Alexa, pergunte Execute Comando executar desligar pc."