@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." [image: 1602941272206-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."

@Keylor-García, please make sure you're copying the whole token and no extra characters. I wonder if there's a firewall blocking the agent from reaching the www.triggercmd.com servers. Are you using a software firewall built into your Antivirus software by chance?

Thanks @gfmendes. I don't know why certain words would work better. The TRIGGERcmd Smart Home Alexa skill simulates a light switch for each command, so I thought ligar and desligar would work best. Google Translate tells me those are the translations for "turn on" and "turn off" which is how I tend say it in English. I can also say, "calculator off". This page gives some background too if you're interested: https://www.amazon.com.br/gp/help/customer/display.html/ref=hp_bc_nav?ie=UTF8&nodeId=201749260

@EmilianoCamara, please open Startup Apps and tell me if it's listed there. [image: 1602158107420-07a98103-bc73-428a-b28f-cacd75cfd8aa-image.png] Please also check whether the the TRIGGERcmd Agent icon is in this folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp If it's not there, you could copy it there.

@Victor-Medeiros, what have you tried? Which skill are you using? Did you try unlinking and re-linking?

@Raphael-Cazelatto, what if you open a cmd prompt first, then run that triggercmdagent.bat script? Can you send me a screenshot of that? I'm sorry nothing is working for you.

Here how it looks on my TV [image: 1601939332287-whatsapp-image-2020-10-05-at-20.07.18.jpeg]

@Raphael-Cazelatto, this installation method was meant for 32bit Windows, but it would work fine on 64bit Windows, and it would allow you to install it to any folder. It also wouldn't show a tray icon. https://www.triggercmd.com/forum/topic/99/no-gui-triggercmd-agent-that-works-on-32bit-windows I'm curious about your use-case. Why do you want to hide the tray icon and install in a different folder?

Thanks @Byron-Trantham.

@Terry-Ap, I don't understand yet. You can add as many commands as you want. Are you trying to find the actual command to silence (aka mute) your computer? I don't know what "block" would be. Also, what operating system are you running?

@Csaba-Ferenc-László, yes, I will try. Next time the error happens, please post the time and day here. That would help me find the problem in the logs. Also please try this - instead of using "Reconnect account" use "Unlink account", then re-link. I found an error in the Google logs that might be giving me a clue, but I need more time to research and test it. BTW, it's ok to have a different email addresses for your Google Home and TRIGGERcmd accounts. EDIT: I think I found the root cause and fixed it today, 9/12/2020 at about 12:30pm EST. You might have to re-link one more time, but after that it should stay linked. Thank you for reporting the problem. After adding logging for this problem I see it was also affecting Alexa users.

@igurman, I answered here.

@Russ NOOOOOOOOO!! jajajajja okey thanks, found the file!! thx dude

@Web-em-Segundos, there's one thing that I know can cause that problem. If you link an Alexa/Amazon account to your TRIGGERcmd account, then link another Alexa/Amazon account to the same TRIGGERcmd account, the first Alexa/Amazon account will stop working. Is it possible that's happening to you?

@TomberWolf, good question. You can have TRIGGERcmd run a "curl" command that calls the IFTTT Webhooks API to run an applet that turns your SmartThings switch on. You'll need your IFTTT webhooks key, which you can get at this page: https://ifttt.com/maker_webhooks/settings You'll see a URL like this: https://maker.ifttt.com/use/**asdfasdfblahblah** The bold part of that URL is your webhooks key. Setup a TRIGGERcmd command like this, where front_light is your Webhook applet's Event Name. curl https://maker.ifttt.com/trigger/front_light/with/key/asdfasdfblahblah When you make your applet, search for Webhooks as your This part. [image: 1598488127745-85f37092-5ae6-47a6-b3eb-b2f75ff0e684-image.png] [image: 1598487955208-e0c34fde-96a7-45ce-960d-170a17cd0ba1-image.png] If you use Windows, you can download curl from here.

@jpe81, for Docker, these posts might be useful to you: https://www.triggercmd.com/forum/topic/780/how-to-reduce-size-by-removing-dubious-dependencies/4 https://www.triggercmd.com/forum/topic/451/run-the-triggercmd-linux-agent-in-a-docker-container It should work fine on Alpine Linux. The agent.js script really just needs NodeJS to run.

@Sync-Crazy Yes you can. Search in the forum. Here my examples: Close apps { "trigger": "Cerrar Calculadora", "command": "taskkill /f /im Calculator.exe", "ground": "foreground", "voice": "Cerrar Calculadora", "voiceReply": "Cerrando Calculadora" }, Restart { "trigger": "Reiniciar en 10 segundos", "command": "shutdown /r /t 10", "ground": "background", "voice": "Reiniciar", "voiceReply": "Reiniciar Desktop" },

@Russ The commands were working on the site, I did what you said and it worked. Thanks!