Posts made by Russ

@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.

Actually, I'll change 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)

That's interesting @gajahduduk. I'll need to do some research. I didn't know about this issue until you mentioned it here, so thank you for telling me.

As always, I recommend you switch to the TRIGGERcmd Smart Home skill unless you have a specific use-case for the Trigger Command skill.

@Cristian-Dindinelli, yes so far I haven't been able to get it working after the recent change Samsung made.

@TheDreamer68, give me some time to look into this. I'll get back to you soon. So far it seems SmartThings broke this integration recently. I'm finding their new system does not synchronize with the "My Testing Devices" list in the SmartThings app.

I created a new Schema App and found it doesn't show up in the SmartThings app under "My Testing Devices."

I also migrated one of my existing Schema Apps using the smartthings schema:update command, but it doesn't work. I also renamed it and the new name doesn't show up in the SmartThings app under "My Testing Devices."

@Fabrizio-Holstein, does it start if you run it manually?

If not, please try renaming your c:\Users\(your user)\.TRIGGERcmdData folder, and then re-run the triggercmd agent. It will prompt again for the token.

Well, it will update most things anyway.

winget upgrade --all

Thanks @Leron-Tolmachev .

@Leron-Tolmachev, I don't know why the direct from HA path isn't working. I'll see if I can reproduce the issue, but in the meantime I suggest disabling it so you can trigger commands from HA via the Internet. It seems like the connection from the agent to HA isn't working. Maybe I need to add logging to determine that.

@Leron-Tolmachev, I'm not sure why it's working via the Internet but not direct from HA.

Can you try triggering a different command? Like the built-in calculator command?

Also, if your command has parameters enabled, please try disabling parameters. I'm worried the "on" or "off" parameter is getting tacked on to the end of your command and messing up the command, although I'm not confident in that because if that was the problem, it should happen either way - direct from HA, or via the Internet (via the triggercmd.com cloud system).

FYI, that "Ignoring duplicate trigger" is saying it got a trigger via triggercmd.com but ignored it because it originally came from HA, and you have the direct HA integration enabled.

Can you share your command? Or ideally a screenshot from the GUI Editor? I'd like to see if I can reproduce it on my Mac.

@Xander, awesome. I'm glad that worked.

@trinib, I can't reproduce the problem with version 1.0.47. For me, within 10 seconds, it always transitions from "Waiting for internet" to the full menu after I re-enable wifi. It get the same result whether I rebooted without wifi or just closed and re-opened the agent without wifi.

I don't use the background service (aka the TRIGGERcmdAgent windows service). I'll enable that and do more testing, but that shouldn't effect the tray icon because it's only for the foreground agent.

FYI, the background service is not necessary unless you want to be able to run command while you're logged out. Most people don't need it.

@Leron-Tolmachev,
I just realized you're not saying the command doesn't run. So please confirm: the command runs when you trigger it from HA, but it doesn't log "Command ran" in the runs list, correct?

If so, that's a known issue with sending triggers direct from HA to the agent. The agent doesn't report that the command ran if the trigger came from HA. There wasn't an efficient way to report it because the ID of the command isn't available in this direct local LAN offline context. If you need to see Command ran logged, you should disable the offline HA integration in the agent config.

HA does still send the trigger to triggercmd.com though (which is logged in the Runs list) so cloud integrations (Zapier, Alexa routines, IFTTT, Make, etc) will still trigger if HA can access triggercmd.com when the command is triggered.

@Leron-Tolmachev, if you have parameters enabled, please try turning that off because that might explain why it works when you click the green Trigger button on the triggercmd.com website and it doesn't when you run the command via Home Assistant locally.

If parameters are enabled, Home Assistant will send on or off as the parameter, so " on" or " off" will be appended to the end of your command, which could be producing an invalid command.

Alternatively you could fill in the Off Command field, and that command will run when you toggle the HA switch off.

@Leron-Tolmachev, awesome. Thank you for confirming that works.

For the offline config, did you generate a long-lived access token from this page?
http://homeassistant.local:8123/profile/security

And you pasted that into the that Home Assistant Token field in your Home Assistant Offline Configuration page?

Also, you can check your ~/.TRIGGERcmdData/debug.log file for clues.

@Leron-Tolmachev, good, thank you for confirming that's working.

If you've enabled the Home Assistant Offline Configuration, please try disabling it, then restart the agent. That should allow the agent to run your commands via the Internet (HA -> triggercmd.com -> agent).

I'm thinking maybe the agent is ignoring the commands from the triggercmd.com server because the offline configuration is enabled but not working yet. It does that to avoid running your command twice - once directly from HA, and again from triggercmd.com.

If you want to get HA offline to work, please confirm your Home Assistant server is accessible at http://homeassistant.local:8123 from your laptop.