@EmilianoCamara, please open Startup Apps and tell me if it's listed there.

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

85f37092-5ae6-47a6-b3eb-b2f75ff0e684-image.png

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!

@raffles-hogan, as far as I know, there's no way to invoke an Alexa skill or Google Assistant action without saying the wake words like "Alexa" or "Hey Google" first.

About pressing a key - you would have to create the scripts folder and create the script that presses a key. Also, if the computer is actually off, nothing can run on it. I think the post you read was about turning the monitor on.

This page lists all the ways you can trigger commands. I pasted the section that shows the Smart Home and original skills here:

Smart Home voice assistant skills (Example: "Hey Google, turn on calculator")

"TRIGGERcmd Smart Home" Alexa skill "TRIGGERcmd Smart Home" Google Assistant action

Original voice assistant skills (Example: "Alexa, ask TRIGGERcmd to run calculator"):

Alexa skill Google Assistant action

@Russ Jajajaja, that's happens... my father says thank you Alexa too and thank you google.

@Russ said in Google Assistant can't recognize TRIGGERcmd:

@안형근 , I see from your screenshots that you seem to have done everything correctly, but I worry it won't work in your area if you can't search for TRIGGER C M D in the directory and find it. You could try one more thing: please try saying, Alexa, talk to TRIGGER C M D. If that works one time, I think Google Assistant is more likely to associate this phrase with the TRIGGERcmd action: "Alexa, ask TRIGGER C M D to run Calculator".

Another idea is to try using IFTTT's webhook system to call the TRIGGERcmd API. Then you should be able to say, "Alexa, trigger X", where X is the "specific phrase" you'd use with the Alexa "Say a specific phrase" option in your IFTTT recipe.

Here's an article about how to use IFTTT with TRIGGERcmd:
https://www.triggercmd.com/forum/topic/31/how-to-use-ifttt-with-triggercmd

Either way keep up the excellent quality writing.