Posts made by Russ

@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"}

This screenshot doesn't show the room I could see while in VR. Apparently the Quest filters that out of screenshots.

I placed a switch in my room and now I can turn it on in VR to run Calculator on my "NewLaptop" computer via TRIGGERcmd.

It's pretty cool, but it needs work. It's opensource. I downloaded it for free and installed it with SideQuest, but you can also install it from the Meta Quest app store for $5. It reads your devices from your Home Assistant server.

https://immersive-home.org/

@gajahduduk, that's great. Thank you for testing it and letting me know.

@Jordel-Miranda, I think you have something in your commands.json that's causing the issue. Please try renaming it. It's in this folder:

C:\Users\(your user)\.TRIGGERcmdData

@gajahduduk, ok - you're right you do have to use one the Trigger Command, TC, or TRIGGERcmd skill to hear the result of your command.

To answer your question about adding that to the new TRIGGERcmd Smart Home skill - no, it's not possible.

@gajahduduk said in Trigger a command with a Shortcut via Siri:

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{} ~/.TRIGGERcmdData/sendresult.sh {}

Can you help me get started? I tried your command it doesn't seem to work. Is there something I need to do in the Music app first?

russ@macbook-air ~ % 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'
60:64: execution error: Can’t make name of «class pTrk» of application "Music" into type Unicode text. (-1700)