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

    TriggerCMD skill working, but not directly

    General Discussion
    5
    22
    1.7k
    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.
    • R
      rafaelramon @Russ
      last edited by

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • P
        PedroMartins
        last edited by

        I was facing the same problem, but solved while writing this:

        If I use the old skill and say "ask trigger CMD to run terço" it works perfect, also works from pressing "trigger" in the website.
        If I use the new skill and say "turn on terço" it doesn't.

        What have I tried:

        • Disabling and enabling the skills.
        • Deleting and adding the command again.
        • Removing and discovering the comands again in Alexa.
        • Removing and re-installing the triggercmdagent.
        • Changing voice command.

        Useful info:

        • Only happens to that command, all the other works fine.
        • This command is a bash script that open a few chrome pages depending on week day.
        • I'm using Linux (PopOS 20.04).
        • I'm using it in portuguese.

        Then I decide to try changing the Trigger name. I used "batata" (potato in portuguese) and it worked, then I tried "Terço" again and it didn't, then I tried "Terco", it worked. Apparently it is a problem with "ç" in the trigger name (in the voice command is working well). Since english don't have that, it's understandable. It's not a big thing or really a problem, just wanted to inform so if anyone is having the same problem, try that.

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