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
@Pierce-Ó-Brádaigh the 10 minute delay is a spam prevention mechanism. most spammers will not wait. these are the attempted logins of spammers for the last several days. It's gone as high as 1300 in the past
