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

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

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

@Russ yes, when I run manualy it start.

@Cristian-Dindinelli said in New SmartThings integration (2023):

hi, i just changed my pc and i messed up everything so i deleted triggercmd from smartthing, but now i can't install it anymore. This link https://developer.smartthings.com/workspace/projects/new won't make me create a new project but send me to an other page.

After some extra step, I could connect to smartthing, but only devices with "voice" command are shared, any advice?

Thanks @Leron-Tolmachev .

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

@Russ There has to be a way. Many systems, like VNC for example, use this feature.

@Carlos-Junior, you could create a script with two commands in it like this:

Then your command would run that script with a command like this:

If you don't want to create a script, you can generally run multiple commands with one command line by separating the commands with && like this:

@kellanist, great. That makes sense.

@Tiago-Ivanov-Lavinas, great. Not sure what happened the first time, but renaming that folder is like a fresh agent install.

@Adam-S It worked. Thanks.

@Diego-Ulises-Pérez-Ruiz, maybe you need to specify the full path to nircmd.exe in your command, like c:\tools\nircmd.exe ...

Also, by manually, I assume you mean when you run it manually from the command line it works. What if you run it manually via TRIGGERcmd using the green Trigger button on the website, or from the green Play arrow in the GUI Editor ? We should make sure those work before attempting Alexa.

Thanks @Xander. I'm glad that worked.