@Mauro, yes, you can start an Alexa routine whenever you trigger a command.

It requires the TRIGGERcmd Smart Home alexa skill to be enabled, then you can

These are the instructions:
https://www.triggercmd.com/forum/topic/1844/run-an-alexa-routine-when-a-command-runs

This video also shows how it works:
https://youtu.be/nrqj-OwDpGE?si=xuuR4yfWZZho9Dqw&t=199

; Defina a cor do pixel que você deseja localizar (no formato RGB hexadecimal)
CorPixelDesejado := 0xd5492a ; Por exemplo, vermelho

; Use a função PixelSearch para localizar o pixel
PixelSearch, EncontradoX, EncontradoY, 0, 0, A_ScreenWidth, A_ScreenHeight, %CorPixelDesejado%

; Verifique se o pixel foi encontrado
If ErrorLevel = 0
{
; Movimente o mouse para as coordenadas encontradas (X, Y)
MouseMove, %EncontradoX%, %EncontradoY%

; Clique no pixel Click

}

; Sair do script após a execução do macro
ExitApp

@HeeHang I know nothing about Make.com but TRIGGER cmd runs windows cmd commands and Windows has the parts to make it possible. Basically you probably want to add something like the following to a cmd/bat file and run that from TRIGGERcmd

start "" app.exe /s timeout /t 5 taskkill /im app.exe /f start runs app.exe in a new process timeout waits a few seconds before returning taskkill /im kills task by name - assuming it is only one

If you have a script rather than an exe the run: cmd /c "my.cmd"

Hope that helps

@Russ yay! I'll give it a go

@Russ It makes sense, thank you again. I will try this as soon as possible but I'm hopeful it'll finally work as I intended

@Russ Oh, I must have misunderstood, they seemed to in the articles I linked. Oh well, shame and very limiting to skill creators. may words get pick on my Alexa for other purposes - eg play - so it's hard.

@Pedro-Dias-0 said in "FN + Page Up":

é possível criar um comando no arquivo .bat para executar essa função do teclado? "FN + Page Up"

Some programs like AutoHotkey can be called to simulate key presses.

However FN keys are usually invisible to Windows and used by the manufacturer to do hardware specific things. Maybe check if AutoHotkey can simulate the FN key.

@Russ Certo, vou tentar

@william-siqueira, thank you for the screenshots. That helps.

Notice the data folder for the background agent is in root's home folder, not your williams user.

/root/.TRIGGERcmdData

I also see No token exists. Login to request one. So you can probably fix it if you run:

sudo su - triggercmdagent --console (paste in your token)

Or you could copy your /home/william/.TRIGGERcmdData folder to /root/.TRIGGERcmdData so it won't create a second computer in your account because you already have a computerid.cfg file in /home/william/.TRIGGERcmdData and the background agent that will run as root will use that computer id.

@Steve-Lee, thank you for doing that!

@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.