Categories

  • Announcements regarding TRIGGERcmd

    69
    Topics
    208
    Posts

    RussR

    @Diego-Guerra, can you send me screenshots of your SmartThings values in your profile and the connector you created in your SmartThings account? I want to see that they match. Send them via the Forum chat to keep them private.

  • A place to talk about TRIGGERcmd

    613
    Topics
    3.0k
    Posts

    RussR

    @marciosenaf, for the TRIGGERcmd Smart Home skill to create devices, your commands need the voice field filled in, and the computer needs the voice field field in unless it's your default computer.

    I suspect your first computer was the default computer but your new one is not. If so, you could fix this by setting your new computer as your default computer in your profile.

    Click your name in the upper-right, and click Profile, then use the Default Computer pulldown to select your computer.

    6bac0cd6-45e0-472c-af6a-4da8221a0f99-image.png

  • A place to share commands you like to trigger remotely.

    Raspberry Pi Mac Windows Linux
    347
    Topics
    1.4k
    Posts

    RussR

    @Anderson-Lajes, I installed the TRIGGERcmd agent on Mint Linux and it worked well for me.

    7d6443d8-bbc9-4e14-8ac8-003a7335fb63-image.png

    If you run it on Hyper-V, you'll want to use a Generation 2 virtual machine, and disable secure boot.

    Also, to use the Background Service you'll need nodejs installed:

    sudo apt install nodejs

  • Instructions for each operating system, and various scenarios.

    API Google Home Alexa Mac Linux Raspberry Pi Windows
    219
    Topics
    1.0k
    Posts

    RussR

    @fabriziotoniolo , sorry about the trouble.

    Thank you for the screenshots. That helps. Please try these things and let me know what happens:

    Close and re-open the TRIGGERcmd Agent, then check for the missing commands on the triggercmd.com website. Change the name of one of your commands, and see if it reflects that change on the triggercmd.com website.

    If none of that works, you can create a new computer by deleting your computerid.cfg and token.tkn file in your C:\Users\(your user)\.TRIGGERcmdData folder, then close and open the TRIGGERcmd Agent. It will prompt for a token like when you first installed it, then it will create a new computer in your account with the same commands (stored in commands.json). Then you can delete the old computer and set your new computer as your default from your profile page.

    FYI, you don't actually have to give your computer a voice name if you only have one computer because your first computer is automatically your default computer, and your default computer doesn't need a voice name to create the Alexa devices. It doesn't hurt to give it a voice name though.