@Mauro I'm glad you figured it out.

@Russ

aha - my bad!

I had voice set to "mac pitch" for both.

I could have sworn voice was ignored for Smart Home and trigger became the device name.

@william-siqueira, first you could make sure the default commands you have in your commands.json run when you click the green Trigger button in your account.

The background commands (the commands with ground = background) will run if you've installed the background service using installdaemon.sh, but you'll need to use ps -ef to check whether they ran because they don't run in the foreground where you can see them.

After that, you can add your own commands by copying one of those lines, and editing the command field to be your own command.

@Sadiethompson, can you be more specific? What problem?

@Russ Sorry for being unclear.

Yes the smart home skill.

Ah. So the device name appears to be the Trigger field and as I used the same for both fields all is good 🙂 I hadn;t grokked that Voice was being ignored.

In fact I eventually found I can use two words for device name (trigger field). You have to be careful as uncommon words can be confused and second words like "play" or "run" can get misinterpreted to do other things as Alexa already handles them.

I do not see "on" or "off" passed as parameters, but the Command or Off Command get invoked as expected. Speaking a number, percent or colour do get passed to either command as a parameter as expected.

The voiceReply seems to be ignored by smart home devices and it always says "OK" unless you use the Alexa App setting to make a noise instead. Is there anyway to get the voice reply to work? I expect as you ignore the voice fields the answer is no 😞

btw I found a useful debugging tool is to add a start to my processing cmd file open a window. eg

start "" echo "[%1][%2][%3]"

That helped me fix an obscure reason some variables were not being expanded when the cmd was invoked from TRIGGERcmd but worked fine from the cmd shell.

Maybe the Runs could show the command return value and outputs to stdout and stderr to help debugging? But that would require more server storage I guess.

@Steve-Lee said in Multiple parameters:

doesn't work with a colour, just get error

but "alexa turn notepad green" gets notepad to open green.txt 🙂

@Russ yeah, I meant similar to XSS really - untrusted input getting passed and parsed 🙂 And no way to escape. Thanks for explanation.

@Russ perfect!

@Steve-Lee, sure, I'll add those.

@Ivan-Kuler said in How long to wait after pc starts to run a trigger?:

PC passa direto pela tela de login, sem pedir um nome de usuário e senha

Good morning... why when I come back from hibernation with windows11 through Alexa it doesn't go straight to the Desktop?...it turns on, goes through the BIOS screen and stays idle... i need to press a key for the monitor to wake up... I would like it to enter directly, without having to press a key... any tips?

PS: My PC also goes straight through the login screen, without asking for the username and password.

@zipster1967
do you have a video of how you did it? I have the same problem

@Christian-Vega-G, I saw that you subscribed this morning. I just sent your refund.

@Chirag-Nahata please watch the video on the triggercmd website. It shows one way to create your own command. You can also use the examples included in the GUI Editor.

@sgrzybolowski, you should be able to get that from your PayPal account transaction history.

@Shawndell-Harris, please send me your home IP address via chat. I'll unblock it.

@Emanuel-MAIA, awesome!

@Luz, the agent should prompt for a token the first time you run it.

You could try closing and re-running the TRIGGERcmd agent.
5d9e7eab-855c-40e1-aefe-58aaa65b66af-image.png

If that doesn't work, you could try: close the agent, delete your C:\Users\(your user)\.TRIGGERcmdData folder, and open it again.