TriggerCMD skill working, but not directly

[Nirav]

@Russ I tried turning the skill on and off, I’ve tried saying “Alexa turn on/off calculator” or any other commands none seem to work directly even attempting making new commands and discovering them

[Russ]

@Nirav, I wonder if you disabled and re-enabled one skill, but you're actually trying to use a different skill. If you're trying to say, "Alexa, turn on/off calculator", the skill you're using is the "TRIGGERcmd Smart Home" skill.

This page lists the skills: https://www.triggercmd.com/forum/topic/30/list-of-ways-to-trigger-your-commands

There are actually three Alexa TRIGGERcmd skills:

TRIGGERcmd original skill (Alexa, ask TRIGGERcmd to run calculator)
TRIGGER command original skill (Alexa, ask TRIGGER command to run calculator)
TRIGGERcmd Smart Home skill (Alexa, turn on calculator)

If you're in the US and you're already logged into alexa.amazon.com, you could use this link to go directly to the TRIGGERcmd Smart Home skill:
https://alexa.amazon.com/spa/index.html#skills/dp/B07P1MMFRP/?ref=skill_dsk_skb_sh_0&qid=b8976b50-65ef-40d1-bbf3-e7425c911101

[rafaelramon]

This happened to me too, without changing anything. Running the script manually works, but asking Alexa to run does not work. Does this have anything to do with the recent windows update?

[Russ]

@rafaelramon, no it shouldn't have anything to do with the recent Windows update if you can run the command manually from the Trigger button on the website.

I suspect Alexa isn't recognizing your voice word. What are you saying to Alexa, and what is she saying back?

[Lucas Ribeiro]

I'm also in trouble with alexa, if i use the routine with the command she doesn't say anything and the command doesn't execute, if i try to execute the direct command "turn on suspend" by alexa, she says "sorry it seems there are some error, to control the suspend, try to disable and activate the skill " , I use the TRIGGERcmd Smart Home skill and it worked well, in the last days the problem started, I'm from Brazil

[Russ]

@Lucas-Ribeiro, one thing you can try to troubleshoot is change your voice word, and change it back. That causes Alexa to delete and recreate the Smart Home switch device associated with that command.

If you tell me the exact time you have the problem, I can look through the logs for clues about what went wrong.

[Lucas Ribeiro]

@Russ I reinstalled it on my Windows and disabled and activate the skill back in and it's working. If it stop, I'll be back here to inform you, thank you.

[Russ]

@Lucas-Ribeiro thank you.

[rafaelramon]

@Russ Alexa is working perfectly, she returns saying that the command was executed, but nothing happens ... Even if you execute the command manually by clicking on the Routine play

[Russ]

@rafaelramon, does it work if you click the Trigger button on the website?

Also, is under View Runs, does it say, "Trigger sent from Alexa Smart Home"?

[rafaelramon]

@Russ said in TriggerCMD skill working, but not directly:

Trigger sent from Alexa Smart Home

When executing the command on the website or in the GUI command, the action is executed, the problem is in the communication between Alexa and Trigger, and it happened overnight without any action by me.
I have already changed the name of the Alexa call, I have already uninstalled the "Alexa Smart Home Trigger" and installed it again, I have reconfigured everything, but nothing solved the problem;
When clicking on an action managed by Alexa, she returns saying that the routine was executed but nothing happens.

[Russ]

@rafaelramon, that helps.

This is the flow:
Alexa Routine -> Alexa TRIGGERcmd Smart Home device -> TRIGGERcmd server -> TRIGGERcmd agent -> command

You just confirmed these parts work fine: TRIGGERcmd server -> TRIGGERcmd agent -> command

Before we work on the Alexa Routine part, we need to make sure this part works:
Alexa TRIGGERcmd Smart Home virtual device -> TRIGGERcmd server

If you go to https://alexa.amazon.com, under Smart Home, Devices, do you see the device for the command you want to run?

They look like this:

Even if you do see it, you should try clicking Remove All, then Discover to re-discover your commands.

One possible reason for the problem is you might have two commands with the same voice word that are conflicting. Please check that.

One way to troubleshoot is backup your commands with a copy/paste from the Text Command Editor to another file, then delete all of your commands except the one you're trying to work on. That way you'll know it's not an issue with two commands conflicting.

[rafaelramon]

@Russ Accessing the page, I see all the devices, exactly as they should.
I don't have a command with the same voice, but when doing the test and deleting the routine and also in the Trigger GUI and redoing the command again.
What happened was strange, since I didn't make any changes, it just stopped working.
So, I think the solution is to erase everything and redo it ... Thank you.

[Russ]

@rafaelramon, one thing you could try is to delete your computer from your account then close and open the agent. It will prompt you again for your token. When you enter the token it will recreate your computer with all of your commands.

Maybe that would fix the Alexa issue because it would recreate your Alexa devices.

[rafaelramon]

@Russ this solved my problem, all the rules were working again. thanks for your attention and patience.

[Russ]

@rafaelramon, awesome. I still wonder what happened though.

[rafaelramon]

This post is deleted!

[PedroMartins]

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.