@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.
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.
@Convaiyer Every trigger has a Paywall button. I've had no luck thinking of a way to use it because who wants to pay me to run a command on my own PC? I mean, you'd have to pay me to play Fortnite but other than that 
@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.