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 this is strange. Sorry about this trouble but I think we can figure it out.

    Can you tell me which version of the agent you have? Right now the latest is 1.0.32.

    I suggest you basically start over. To do that, rename your current .TRIGGERcmdData folder and close and open the TRIGGERcmd agent. It will re-prompt for a token then it will create a new computer. Delete your old computer record from your account after you confirm the commands are syncing.

    After that, you can restore your commands by copying your commands.json from the renamed folder.

    You'll probably want to make your new computer record your default computer too.