TRIGGERcmd
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Triggercmd stopped working.

    General Discussion
    3
    5
    423
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Luis Eduardo Klein de CarvalhoL
      Luis Eduardo Klein de Carvalho
      last edited by

      My Alexa regonizes all the commands and qhen I edit them, she says she foudn a "new" commands.
      My commands on the Triggercmd client are working when a run them on Command Editor (when I play the little green play button).
      I have, not only one, but two triggercmd skills on my Alexa (tested with both and with either only and nothing works).
      My account is fine and my desktop shows there.
      Everything seems to work, but when I run a routine with a triggercmd command, it does not work. The command does not run on my PC.
      Any help?

      RussR 1 Reply Last reply Reply Quote 0
      • RussR
        Russ @Luis Eduardo Klein de Carvalho
        last edited by

        @Luis-Eduardo-Klein-de-Carvalho, you should troubleshoot in this order:

        1. Run it locally with the play button in the GUI editor - you confirmed that works.
        2. Run it via the Trigger button on the website - does this work?
        3. Run it via the TRIGGERcmd Smart Home Alexa skill with Alexa, "turn on X"
        4. Run it via the Alexa routine.

        The original Alexa skills don't work with routines. Only the Smart Home skills do. This page lists all of them.

        Russell VanderMey

        1 Reply Last reply Reply Quote 0
        • Neto GerbiN
          Neto Gerbi
          last edited by Neto Gerbi

          @Russ said in Triggercmd stopped working.:

          Run it via the TRIGGERcmd Smart Home Alexa skill with Alexa, "turn on X"

          I'm with the same problem. I'm using TRIGGERcmd on Debian 10.
          Steps 1 and 2 works fine. I couldn't find the 'X' of step "3. Run it via the TRIGGERcmd Smart Home Alexa skill with Alexa, "turn on X""

          Alexa founds one device for each command defined in TRIGGERcmd. If I say the command i defined in TRIGGERcmd, sometimes Alexa doesn't understand or executes another thing. ie.: I created a command that the name is open editor and defined to open VScode... step 1 and 2 ok, alexa connected to this device with the same name (open editor). When I say "Alexa, open editor" she says something like... "Trying to find for musical editor in google play".

          Other command is "restart computer", alexa responds "Restart computer is not compatible with this".

          any help?

          RussR 1 Reply Last reply Reply Quote 0
          • RussR
            Russ @Neto Gerbi
            last edited by Russ

            @Neto-Gerbi , the "X" above is meant to be a placeholder for your command's voice word(s). So the correct phrases if you're using the TRIGGERcmd Smart Home Alexa skill are these:

            "Alexa, turn on open editor" and "Alexa, turn on restart computer"

            That's because the TRIGGERcmd Smart Home Alexa skill created a virtual switch device (like a light switch) called "open editor" and "restart computer" and you're telling Alexa to turn the switch on or off.

            Russell VanderMey

            Neto GerbiN 1 Reply Last reply Reply Quote 0
            • Neto GerbiN
              Neto Gerbi @Russ
              last edited by

              @Russ Worked...thank you very much!!! Awesome!

              1 Reply Last reply Reply Quote 1
              • First post
                Last post