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