R
Online
@Thiago-Rodrigues, I think you'd have to run 2 commands:
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.
@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
Enable Wake-On-Lan in your BIOS or UEFI.
Enable Wake-On-Lan in the Agent.
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:
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"
}
}
]
}
]
}
}
I updated the Roku app. Now it groups commands by computers, or panel buttons by panel.
Reminder, the app shows computers and commands if this checkbox is unchecked on your profile page:
It shows panels with their panel buttons if you check the checkbox.
FYI @mlabombarda
@Vinicius-Gimenez-Figuerola if you rename your command, and rename it back, it will re-create the Alexa device with this new UI option to disable the doorbell press notifications. Does that solve it? I tried to default it to false, but there doesn't seem to be a way to do that.
@Vinicius-Gimenez-Figuerola , interesting. What triggers that routine? I would think the command couldn't trigger it because it would be too late. I'll try it.
EDIT: I tried it - that works, but I don't want everyone to have to do that for every command, so I'm still looking for a solution. Worst case, I could make the doorbell feature (for running routines) a toggle for each command, and default it to false.
EDIT2: I added a feature to each device to allow you to disable the "Doorbell Press Notifications".
@Vinicius-Gimenez-Figuerola, I noticed the same thing yesterday. When I trigger a new or changed command via the virtual Alexa Smart Home device, my Echo device says, "Ding dong, someone is at [voice word]." Old commands are not affected.
For now, I set my Alexa device to "Do Not Disturb" so I don't hear the announcement like this article suggested:
https://www.amazon.com/gp/help/customer/display.html?nodeId=GV7ZJNSWKL8E3D7T
I'm looking into what changed. I think Amazon changed something recently because I didn't change anything related to the doorbell feature. You probably know this, but the doorbell feature is needed to trigger an Alexa routine when a command runs.
It doesn't have anything to do with the Voice/MCP Reply field. The TRIGGERcmd Smart Home Alexa skill doesn't use it. Only the legacy conversational Alexa skills (called TRIGGERcmd, Trigger Command, and TC) use it.
I opened a case with Amazon about it.