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

    Alexa+ (Alexa Plus) breaks TRIGGERcmd custom actions in new routines, while existing routines still work

    Scheduled Pinned Locked Moved General Discussion
    1 Posts 1 Posters 2 Views 1 Watching
    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.
    • UuzzU Offline
      Uuzz
      last edited by

      Hi,

      I've been using TRIGGERcmd with Alexa for a long time to execute commands on my Windows PC through Alexa routines. Everything worked perfectly until Alexa+ was introduced.

      My setup uses a single TRIGGERcmd command named parametro, which executes a batch file (alexa_actions.bat) and accepts parameters to determine which action to perform.

      For example, this is the custom action I use in my Alexa routines:

      Spanish (my actual configuration):

      preguntarle a Ejecuta Comando ejecutar "parametro" con parametro modojuego
      

      English equivalent:

      ask Trigger Command to run "parametro" with parameter modojuego
      

      The parameter modojuego is passed to my batch file as %1, which then executes the corresponding action.

      The issue

      All my existing Alexa routines created before Alexa+ continue to work perfectly, including those that pass parameters to TRIGGERcmd.

      However, when I create a new routine using the exact same custom action, Alexa+ fails to execute it.

      I've tested the following:

      1. Creating a new routine using the same Spanish command structure as before.
      2. Copying and pasting the exact custom action from an existing, fully functional routine into a new one.
      3. Trying alternative Spanish phrasing.
      4. Trying the English command syntax.
      5. Invoking the TRIGGERcmd skill directly by voice, without using a routine.

      All these attempts fail, while the original routines continue working normally.

      Alexa responds with messages such as:

      • "I can't execute that command. There seems to be an error with the request."
      • "I can't help you with that right now."
      • "This request is not available."

      Expected behavior

      New Alexa routines should be able to invoke TRIGGERcmd and pass parameters just like existing routines.

      Actual behavior

      Only routines created before Alexa+ continue to execute successfully. New routines fail even when their custom actions are identical to those in working routines.

      This suggests that Alexa+ may be handling third-party skill invocations differently, while preserving compatibility with previously created routines.

      Question

      Is this a known compatibility issue with Alexa+? Is there any workaround that would allow me to continue using the original TRIGGERcmd skill with parameters in new Alexa routines?

      I'd prefer to keep my current setup rather than migrate to the Smart Home skill, since I use a single command with multiple parameters to control different PC actions.

      Thanks!

      1 Reply Last reply Reply Quote 0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      • First post
        Last post