@Luisito-Palma, makes sense. You're welcome. Your project looks interesting.

@fcovalls, please check/try these things:

Make sure each computer has a unique Voice Name value or is your default computer. Make sure each command has a Voice field set. If you have one computer that's misbehaving, try renaming it and renaming it back. That will force Alexa to re-create the devices. Try changing your default computer from your profile page. Confirm you see the Smart Home Voice Commands page to make sure you see it there. If you don't see it there, Alexa won't create a device for it, so troubleshoot that first.

Are you asking for a way to fire off triggers from your phone?

You can create a panel of the specific triggers then add a shortcut to panel’s url to your phone’s Home Screen

Or

Install ifttt on your phone and fire them off some other way like sms.

@Frank-Malczewski, thanks for letting me know. Sorry that's necessary but I'm glad it's working for you. I've seen those extra tray icons before - the icon doesn't get removed when you kill the agent without using the Quit function.

@David-0 under Edit Profile I see Change Password. I think if you unlink your Gmail account you'll still be able to login with your username and that password. You should try logging in with that before unlinking just to make sure first.

@David-0, good. I think that makes sense in your case.

@Russ I managed to make it work, I found the application that launches Trigger CMD by searching in the file manager. Thank you for your support.

@Russ It's a swiss army knife on it's own. Paired with TriggerCMD it's a Bazooka.

@Russ Thanks! Already resuscribed, wont happen again!

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