@Edwin-Zahra, if you edit the Alexa device, can you flip the "Doorbell Press Notifications" switch off? See the screenshot above.

That doorbell press is necessary to run Alexa routines when your commands run.

@Edwin-Zahra, I'm glad you figured it out. You did the right thing - because you haven't subscribed, you can only have one computer, so you had to delete the old computer before you could add the new computer.

An alternative would have been to copy your ~/.TRIGGERcmdData folder from your old computer to your new one. That would have copied your commands.json and your computerid.cfg file which contains your computer ID. That computer ID is what connects your computer record to your actual computer running the triggercmd agent software. It's not the MAC address - it's that computer ID.

Also, yes, whether it's your old or new computer, if you check the "Create Alexa Smart Home device for this computer" checkbox you can say Alexa, turn off X, where X is your computer's voice name.

Thanks @igorneth!

@hlombard thank you for reporting it. I'm looking into it now.

I can't seem to reproduce the problem (yet).

Can you tell me which MCP connector you're using? Is it the stdio one or the streamable http one?

Can you send me a screenshot of runs list for a command that had the problem?

You might want to uncheck this on your profile page for now if the emails are annoying you.

@Thiago-Rodrigues, I think you'd have to run 2 commands:

1. Turn on the computer and wait for it to boot.
2. Turn on the monitor after the computer is booted.

For #1, you could run the wakeonlan or WakeMeOnLan command from a separate computer on your network, or use this new Alexa method.

For #2, I would not use TRIGGERcmd - I would use this method to turn on my monitor whenever the PC boots up:

@igorneth, if you close and open the agent it should download the updated list of examples.

@igorneth, I added it. Let me know if you want me to make any changes.

@igorneth nice job!

@dinco fyi, now Alexa can send the magic packet so you don't need to run the wakeonlan command.

https://www.triggercmd.com/forum/topic/3377/alexa-wake-on-lan

@holmstockd, fyi, now you don't need a second computer on your network. Alexa can send the magic packet. This explains how:

https://www.triggercmd.com/forum/topic/3377/alexa-wake-on-lan

@Stanisław-Grzybołowski, I sent it just now.

@Marcus-Mortensen, I found your Paypal TRIGGERcmd subscription and cancelled it for you.

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

1. Enable Wake-On-Lan in your BIOS or UEFI.

2. Enable Wake-On-Lan in the Agent.
   

3. Enable the computer Alexa smart home device.
   

@Luca-Coraggio, the "TRIGGERcmd Smart Home" Alexa skill is the one you want.

Do you have a device for each command listed in your device list in your Alexa app? You'll need that because that's what you're telling Alexa to turn on/off.

Please try changing your voice word for the Steam command to just "steam" so you can say, "Alexa, turn on steam", or in your case (Italian), "Alexa, avvia steam".

@Hannibal I see an error in the json. There should be a quote (") at the beginning of the word background.

@rsoane, it seems to be up for me. Can you send me a screenshot of what you see?

@Hannibal, I see the problem. I told you /usr/lib/triggercmdagent which is the path on Ubuntu, not Raspberry Pi. Sorry about that. I corrected the "next steps" above to match the instructions here.

It should look like this when you run the triggercmdagent command as root:

pi@fe5978dee0e5:~$ sudo su -
root@fe5978dee0e5:~# triggercmdagent
Run installdaemon.sh to install the triggercmdagent daemon so it runs during boot
Daemon install: false
No token exists.  Login to request one.
prompt: token:

Then run this to install the background agent that will startup as root during boot:
/usr/share/triggercmdagent/app/src/installdaemon.sh

Then edit /root/.TRIGGERcmdData/commands.json and make sure your commands have ground = background.

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.

To enable Wake-On-LAN, enable it in your BIOS and test it, then enable it like this:

Awesome @Vinicius-Gimenez-Figuerola. Thanks for letting me know it's working for you.

You could have Claude run a command each time it finishes a prompt.

One idea: turn a light green when it's finished, and turn it red when it's working on something.

I tend to use the notepad command when I test parameters.

[repo path]\.claude\settings.json:

{
  "hooks": {
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "mcp_tool",
            "server": "triggercmd",
            "tool": "run_command",
            "input": {
              "computer": "New Laptop",
              "command": "Notepad",
              "parameters": "started"
            }
          }
        ]
      }
    ],
    "Stop": [
      {
        "hooks": [
          {
            "type": "mcp_tool",
            "server": "triggercmd",
            "tool": "run_command",
            "input": {
              "computer": "New Laptop",
              "command": "Notepad",
              "parameters": "done"
            }
          }
        ]
      }
    ]
  }
}