That is fine! Thanks everything now works as before…

Or it's possible it's working but you only have the voice field filled in for your "edit" command. That's what determines which triggers show up as devices now. It uses the same logic as the TRIGGERcmd SmartHome Alexa skill and Google Action. If that's the problem, just fill in the voice field on each command you want to show up as a device in SmartThings.

If you send screenshots here that have your secrets, just change them after. Make sure you re-sync up the profile page info with the info in your SmartThings account too of course.

You could also direct message me your screenshots.

Thank you for your patience. I'm sure we can make this work.

In the previous integration I was able to select the triggers that I wanted to be mapped as virtual switches, what is the situation now? why dont I see my triggers in the smart things integration?

Thanks!

I considered selling a hardware device, but when I asked them about it, they said my users would only be able to use SmartThings to work with that hardware, so that wouldn't help.

I'm working on a new method that won't require SmartThings approval.

I'll post here again when I have it working. I'm hoping by this weekend.

EDIT: I just finished the new SmartThings integration. Please try it and let me know if it works for you.

ERROR: Something went wrong. Please try to install the SmartApp again.

I think something changed in the Samsung site and triggerCMD looks like is uncompatible, is there any way to fix this? I have tried to reinstall the app but there is no way to install a new app using their new UI.

Do you have any idea what is going on?

Thanks!

Handler

It works like a charm!
I have just follow the instructions, and had it immediately working. Still good at 2021

You installed the device handler and SmartApp, correct?

Here's a video showing the process: https://www.youtube.com/watch?v=dq-loAiKAgo

If you still get that error, please post a screenshot. It might help me understand what's happening.

Also, you installed both the SmartApp and the Device Handler, correct?

https://www.triggercmd.com/forum/topic/86/actiontiles-tile-with-triggercmd-bookmark-url/14

It says you can make a small modification to the SmartThings code to make it so the switch goes back off after you flip it on.

i have triggercmd installed in my pc so i can open kodi, but i have a 32bit version so thats why (i suppose) i dont have the option to parse a cmd so the smartthings switch knows when its on or off.

that beeing said when i press the switch it open kodi but it stays on (green), then if i close but manually it stays green forever, if i flip it again it goes off but it opens kodi, cause im not using the script.

well what i want is, can i switch the smartthings switch to a switch that doesnt stay on, it just pushes and goes back to initial state?

thanks in advance

EDIT:
I was able to reproduce the problem. I tested the change and updated the code. Thanks @mthiel for the fix!

// deviceList += ["name" : "${roomName} ${devices?.name}", "did" : "${devices?.did}", "type" : "bulb"]  <- this logic doesn't work when there's only 1 command
// Thanks to mthiel for finding this fix. 
deviceList += ["name" : "${roomName} ${devices[0].name}", "did" : "${devices[0].did}", "type" : "bulb"]

I spent a few hours troubleshooting the SmartApp code and found the root cause around line 249. When a single trigger comes back from the api, the conditional looks like it assumes the type will be a Map, but it actually just returns a List with a single item at index 0. Changing the "devices?.name" and "devices?did" to "devices[0].name" and "devices[0].did" fixes the issue for me. I only realized the problem because the trigger list kept creating devices with brackets around the name, making me expect a typing problem.

It's working great for me now, hope my digging helps!

I recommend you try this:

Go to Marketplace, SmartApps, My Apps, TRIGGERcmd, Next.
Uncheck all of our commands, and click Done, Save.
Go to Home, and if you have any TRIGGERcmd switches left, delete them.
Go to Marketplace, SmartApps, My Apps, TRIGGERcmd, Next again.
Check the commands you and to be switches.
Test your switch again.

BTW, I removed your token from the output you pasted.

I'm trying to get this setup to put my display to sleep, but the commands don't seem to be reaching SmartThings. If I manually fire the TriggerCMD from my phone browser it works perfectly, but SmartThings doesn't seem to be communicating correctly despite the lack of any error. TriggerCMD also doesn't report receiving any requests except the ones I performed from the browser. I don't think there's an authentication issue since the SmartApp is reading my commands fine. I'm not sure what else to check. Here's a snip from the SmartThings log:

57bb48b4-bb6a-48d0-8938-e085928b86e6  4:47:54 PM: debug OFF result: [response:done]
57bb48b4-bb6a-48d0-8938-e085928b86e6  4:47:54 PM: debug Return Code = 200 = Command Succeeded.
57bb48b4-bb6a-48d0-8938-e085928b86e6  4:47:54 PM: debug In apiPost with data: [token:(token), uri:/api/run/triggerByID, body:trigger=[5c61df9baa745900163af4dd-5c64b9eb3b309f00167a06eb]&params=off]
57bb48b4-bb6a-48d0-8938-e085928b86e6  4:47:54 PM: debug Off request from child device
57bb48b4-bb6a-48d0-8938-e085928b86e6  4:47:54 PM: debug ON result: [response:done]
57bb48b4-bb6a-48d0-8938-e085928b86e6  4:47:54 PM: debug Return Code = 200 = Command Succeeded.
57bb48b4-bb6a-48d0-8938-e085928b86e6  4:47:54 PM: debug In apiPost with data: [token:(token), uri:/api/run/triggerByID, body:trigger=[5c61df9baa745900163af4dd-5c64b9eb3b309f00167a06eb]&params=on]
57bb48b4-bb6a-48d0-8938-e085928b86e6  4:47:54 PM: debug On request from child device script_dth_cd2efee0eca44de1d6ceeb8c9ede43c0f5239b6c1e6e37c4e674414c2538f18d@574ae66b

This is what I got when I ran it your way:

sudo -u pi  ~/Smartthings/TriggerCMD/Scripts/Myscript.sh
sudo: /root/Smartthings/TriggerCMD/Scripts/Myscript.sh: command not found

Notice it's translating the ~ to /root before the command runs as pi.

This works though:

{"trigger":"Test","command":"sudo -u pi -H \/home\/pi\/Smartthings\/TriggerCMD\/Scripts\/Myscript.sh first_arg ","ground":"background","voice":"Test","allowParams": "true"},

This is my test script:

#!/bin/sh
echo $2 $1 >> /tmp/log.txt

This is the output:

$ tail -f /tmp/log.txt
on first_arg

My script is as follows:

array=( $1 $2 )
some_command ${array[1]} ${array[0]}

I used an array because I needed to reverse the order of the parameters. Now my commands.json has a trigger configured as such:

  {"trigger":"Test","command":"sudo -u pi -H ~/Smartthings/TriggerCMD/Scripts/Myscript.sh first_arg " ","ground":"background","voice":"Test","allowParams": "true"}

I'm expecting TriggerCMD to pass the "on" or "off" as the second argument, but for some reason, it doesn't seem to be doing so when I test from the website. Am I doing something wrong? I even tried to make a script specifically for the first argument so the only argument needed from TriggerCMD is the on / off, but it still doesn't work.

Turn lights on: heyu fon Kitchen
Turn lights off: heyu foff Kitchen

What I am hoping is that there is something similar to %1, %2, etc in a batch file so that I can write:

heyu f%1 Kitchen

and pass on or off that way, to make the virtual switch work. AFAIK it can only be done with a script, but if there is a simpler way I'd love it since I would only need to edit the json (although a script to parse the on/off along with the device name would be more elegant).

EDIT: Disregard, I'm going to go with a script after all, my OCD wants the most elegant solution.

• -y

• update

  {"trigger":"apt update","command":"apt-get -y update","ground":"background","voice":"update"},
  

BTW, if you leave allowParams out, or use "allowParams": "false", then SmartThings won't append on or off when you flip the switch - it will just run the command without the extra parameter when you flip it on or off.