Categories

  • Announcements regarding TRIGGERcmd

    82 Topics
    226 Posts
    RussR
    If you check the new Create Alexa Smart Home device for this computer checkbox, you'll get an Alexa Smart Home device that you can use to: "Alexa, set X volume to 50 percent" - run the volume control command with 50 (for example) as the parameter "Alexa, unmute X" - runs the mute control command with unmute or mute as the parameter "Alexa, turn on X" - sends a Wake-on-LAN magic packet from your local Echo device to turn on your computer "Alexa, turn off X" - runs the shutdown command X is your computer's voice word, or its name if you don't have a voice word for it. [image: 1784926161256-fe626973-2ba0-4a14-a3db-2cecd59fdab4-image.png] To enable Wake-On-LAN, enable it in your BIOS and test it, then enable it like this: [image: 1784926985471-a4f1bb0c-60dc-49d1-ac78-7b42c1f953d9-image.png] [image: 1784927086303-4d6c0507-4f97-44e6-8819-13b6c5631abd-image.png]
  • A place to talk about TRIGGERcmd

    724 Topics
    3k Posts
    UuzzU
    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: Creating a new routine using the same Spanish command structure as before. Copying and pasting the exact custom action from an existing, fully functional routine into a new one. Trying alternative Spanish phrasing. Trying the English command syntax. 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!
  • Instructions for each operating system, and various scenarios.

    294 Topics
    1k Posts
    RussR
    I made this video to describe the new feature: https://www.youtube.com/watch?v=NKWxyIQT4G8 More info here: https://www.triggercmd.com/forum/topic/3373/new-computer-device-option-for-triggercmd-smart-home-alexa-skill-users?_=1786117895659 Enable Wake-On-Lan in your BIOS or UEFI. Enable Wake-On-Lan in the Agent. [image: 1786121269959-c15bdc1e-8cf9-43e2-adb8-81634841b4d7-image.jpeg] Enable the computer Alexa smart home device. [image: 1786121340761-aca55542-60b1-4f3f-b808-384b094dcb38-image.jpeg]
  • A place to share commands you like to trigger remotely.

    400 Topics
    2k Posts
    igornethI
    @Russ said: I created a separate app for triggering commands called TRIGGERcmd Misson Control. Now you can use it to generate commands using AI - checkout this video. [image: 1772756389075-62116fd1-ae36-4aef-a892-4272194a854e-image.png] Perfect work!