TriggerCMD says that it can't find the computer

  • Hey,

    Even if I say "Hey Google, ask TRIGGERcmd to run chrome", it won't execute.
    This time I am being told that "You haven't set a Default Computer on your TRIGGERcmd profile yet".. and I am damn sure I have!

    Regarding the second issue, that seems to work.

    Edit: Tried reinstalling the program, thinking this might solve the issue and now I can't reuse my token.. due to my stupidity I guess. ;-;

    Thank you and I wish you a Merry Christmas!

  • @ashley12, I see you have 4 different TRIGGERcmd accounts. I think you might have associated the Google account you use for Google Assistant with a different TRIGGERcmd account from the one that was associated with the agent on your computer.

    To get the agent working again, you'll need to do these things:

    • Log into your TRIGGERcmd account - the one associate with Google Assistant.
    • Delete your computer
    • Delete or empty out your .TRIGGERcmdData folder. You'll see that folder if you type %userprofile% into Windows Explorer, or hold the Windows key and press R, then type %userprofile% and press enter.
    • Close the TRIGGERcmd agent, and re-open it.
    • Copy/paste the token in from the Instructions page.

    To figure out which Google account you use for Google Assistant, you can tap the little blue icon in the upper right in the Google Home app, then tap the three dots in the upper right, and tap Account.

    To make sure the correct TRIGGERcmd account is associated with that Google account, you can do the following:

    • Log in as that Google account in a web browser.
    • Go here in that browser:
    • Find TRIGGERcmd and click Remove Access.
    • Go here in that browser and click Allow, or you an just say "Talk to TRIGGERcmd" in the Google Home app and it should prompt you to re-link your account.

    EDIT: Correction - the "Trigger Cmd" entry at shows you the connection you made to your Google account if you log into the website with your Google account. I haven't found a site that shows your Google Assistant login accounts yet.

  • Yeah, I might have too many accs xD in desperate tries to make it work...

    I did all of the steps you mentioned and I still get the same error..

    The funny thing is, on Alexa, the commands work..

    And yes, I've linked the TRIGGERcmd to my account...

    Edit: Nevermind, I tried after 30 minutes or so, and it worked!

    Now I have another (and last, I promise!) question.
    Can I set paths to executables that are not found under the AppData folder? I have a few programs that do not have their exe's under any of the AppData folders and simply setting their path to, let's say, C:\Program Files\so on\so on... won't trigger the command.

  • @ashley12, that's awesome - I'm glad Google Assistant is working now.

    Feel free to ask more question. I'm happy to help.

    About paths to c:\Program Files\so on\so on... That should work, but you have to put quotes around any path that has spaces in it.

    I just tried Windows Media Player and this was the path:

    "C:\Program Files\Windows Media Player\wmplayer.exe"

    One way to easily get the full path with quotes is to find the .EXE file, right-click it, and click "Create shortcut". Then right-click the shortcut and click Properties. The Target field has the full path, so you can copy/paste that into the Command field in the TRIGGERcmd agent.

  • Thank you, everything works now!

    I tried to use the path with quotes yesterday, however it opened the command prompt instead but now it works, haha

    Thank you again for the help and for the nice application that you've created!

  • Hello Ashley,
    Try to make a shortcut for spotify then call that shortcut. It should work.

  • @gcabot
    Hey, I tried this out before @Russ told me how to fix the path, however that didn't work for some reason, but it's all fine now.

    Also, suddenly the system commands stopped working (for example, shutdown, hibernate, etc) and I wonder why since the commands are the standad ones (i.e., command: shutdown /s /t 10; ground: background). The background service is installed too..

  • @asya, if your background commands aren't working you should try restarting your TRIGGERcmdAgent Windows service. You could try switching the shutdown command to a foreground command too.

  • @russ hi i was hoping you could help me out with this...i want to be able to shut down my computer i put the command as shutdown /s but when i ask google home the trigger command service says that it cant find a trigger named shutdown for my pc. could you possibly write out exactly what i would put in the a basic trigger name and everything..? thanks i appreciate anything you may be able to give me on this information

  • @buddahs808 ,

    The trick is to use a simple word for google to hear in the 'voice' field for the command.

    Does 'calculator' work?

Log in to reply