Posts made by Russ

Here I'm using the triggercmd MCP server in goose:

Now you don't have to install the TRIGGERcmd MCP server in Claude or VSCode if you just want to try it out. You can use it right in your browser, if you're subscribed.

Also, as of agent version 1.0.50, a new mcp tool will be added for any command that has an MCP Tool Description:

Your description should explain to the AI LLM what the command does and how to use the parameters. For example:

"This is a color LED light bulb that you can turn on or off. You can also change the color. The parameters are on, off, or a color like red, blue, green etc."

@Fabio, are you able to run your script as a TRIGGERcmd command yet?

You can run it with a command like this:

python3 c:\folder\pyautogui-position\script.py

This should work with any MCP client, but I've tested it with VS Code and Claude Desktop.

This video shows how to set it up and use it: https://youtu.be/4WSN52Optjk

I put the instructions and download links here:
https://github.com/rvmey/triggercmd-mcp-stdio

TIP: Most AI tools give you an option like this Claude setting. This tells the LLM how to use your commands (and their parameters), so you don't have to tell it every time you start a new chat:

@garym77, does that command work from a Terminal window? You should run it there first so you can see if the command gives an error.

Also, you should make the voice word something like creality so you can say "Alexa, turn on creality" after you enable the Triggercmd Smart Home skill.

@Stanisław-Grzybołowski

I emailed you the PayPal transaction info. Hopefully that will serve as an invoice.

For now you can only use it if you run your own n8n community edition server because n8n has not verified it yet. I submitted it to be verified and I'll update this post when/if they do verify it.

@Furkan-Cevik, you're welcome. I just published version 1.0.48. I hope that fixes it, but please tell me if you see it again after upgrading.

@Furkan-Cevik, thank you for reporting it. I have a theory about what's causing it, and I'll produce a new agent version soon.

@Convaiyer, let's talk about it. I just sent you a PM.

@Ron-Hoskins, I upgraded your account to subscribed for now, just so we can troubleshoot this.

The Runs list does not get updated when you're not subscribed and try to run more than one command per minute. Now that your account is subscribed, you should be able to see what command is running more than once per minute.

Let me know what you see please.

@rsxyo, you could try this old mac version. I don't have Yosemite to test it myself, but it might be old enough.

https://triggercmdagents.s3.us-east-1.amazonaws.com/TRIGGERcmdAgent36.dmg

@Strahan, I wonder if when the TC agent runs your batch file, the sql.exe file isn't in your PATH, so it doesn't run. The agent is probably running your batch file, which you've basically already proven with your loghealth.bat experiment.

I like that you added another line to your laundryreset.bat file that writes something to a log file, but it's writing your log.txt file to the present working directory, which in the context of the TC agent is something like this:
C:\Users\russ\AppData\Local\triggercmdagent\app-1.0.47\resources\app\src

Assuming it is running your laundryreset script, you can probably fix this if you put the full path to your sql.exe file (and your log file) in the laundryreset.bat file, something like this:

@echo off
c:\full\path\sql.exe homecenter "delete from activeitems where action = 8192" /u service.triggercmd.homecenter /p (pwd) /h lioth.mydomain.com /l c:\logs\laundryreset.log
echo From laundryreset.bat >> c:\logs\laundryreset.log
dir >> c:\logs\laundryreset.log

You'll want to remove the last 2 lines, especially the dir line, but I put it there because that can show you what the working directory is.

@Ron-Hoskins, I'm glad you figured it out. No need for a donation - I hope you'll subscribe at some point.

@Rodrigo-Carvalho-0, those emails are meant to tell users who don't have a TRIGGERcmd subscription why their command didn't run.

You must have an Alexa routine that's trying to run multiple commands every hour. Could you disable or delete that routine?

Otherwise, I could add an option in your profile page for non-subscribers to disable those emails - they'll just silently fail because you're not subscribed and you're trying to run multiple commands in 1 minute.

@Moacir-Vilela-Sêga, I just uninstalled and re-installed the background agent. I'm using the latest version of the agent - 1.0.47.

You could try rebooting, then trying again.

@chrischickshow, that makes sense. I'll add something about that to the docs to warn people not to use the name of a room in their voice words..

@Moacir-Vilela-Sêga good. Sorry I didn't get back to you but I did test it and it was still working for me.

Nice @gajahduduk. I'm glad you got it working. Thanks for sharing your use-case.

@gajahduduk, the sendresult.sh script is not executable by default, so you could probably solve it by running this:

chmod +x ~/.TRIGGERcmdData/sendresult.sh

Or make your command:

osascript -e 'tell application "Music" to set result to "This song is " & name of current track & " by " & artist of current track & " on the " & year of current track & " album " & album of current track' | sed 's/^/"/;s/$/"/' | xargs -I{} bash ~/.TRIGGERcmdData/sendresult.sh {}

If you run a command like this:

curl 'https://TRIGGERcmd.com/api/run/trigger?computer=maclaptop&trigger=result&token=(your token)'

... and your command has {{result}} in the Voice Reply field, you'll get a response like this:

{"message":"Trigger sent.  Result was: YOURRESULT"}

So your Shortcut will need to parse that message using "Get Dictionary Value".

This post has some detail about it.

EDIT: I changed that response to the following to make it easier to get the command's result.

{"message":"Trigger sent.  Result was: YOURRESULT", "result":"YOURRESULT"}