Hi, I use terminal command to control my Samsung Oven mit SmartThings CLI. The command in the terminal is as follows and it works fine in the linux terminal: smartthings devices:commands <myDeviceID> --token=<myToken> 'main:execute:execute("/mode/vs/0",{"x.com.samsung.da.options":["Sound_Off"]})' …

Try setting the full path to the command. If still not working connect the exec node outputs to the debug nodes, configured to Output Full Message and show us what they show.

That should have read 'connect the exec node outputs to three debug nodes'. You can find the full path to the command (smartthings) using the command which smartthings which will say something like /usr/bin/smartthings in which case the command to use in the exec node would be /usr/bin/smartth…

Hi @Colin thanks for the fast reply. Yes, the full path is this: /usr/bin/smartthings And the filling works in my linux terminal: /usr/bin/smartthings devices:commands <myDeviceID> --token=<myToken> 'main:execute:execute("/mode/vs/0",{"x.com.samsung.da.options":["Sound_Off"]})' Again, when usi…

Interestingly, when I do remove most of the parameters and switch into spawn mode, after sending this: /usr/bin/smartthings devices:commands I do get an instant reply from the remote API: { _msgid: 'd1307f656642a636', payload: 'logging in...', topic: '' } Both myDeviceID and myToken are in forma…

Send the command via msg.payload msg.payload = `smartthings devices:commands <myDeviceID> --token=<myToken> 'main:execute:execute("/mode/vs/0",{"x.com.samsung.da.options":["Sound_Off"]})'`

The Smartthings docs seem to say you don't need the = (ie --token XXXX..) or maybe use a config file to hold the credentials ? Get Started With the SmartThings CLI | Developer Documentation | SmartThings Find the SmartThings CLI source in our GitHub repo.

When passing a command including embedded quotes, in here '..."..."...' through exec node, I wonder if there is not a problem of quotes on what is executed on the host?? I would try to see effectively what is happening on the host by replacing the command itself /usr/bin/smartthings with a shell sc…

Thanks. But the issue does not seem to be just the token, but also the other parameters.

Of course as a work-around I could pack everything into a bash script and just call the script from with my exe node, but this would take some flexibility in sending different commands, that I would like to create later for more advanced use-cases.

Node-RED

Node-RED Forum

Exec-Node: Works fine in Linux Terminal, but not in Exec-Node

General

jbudd 14 November 2024 08:50 6

Can you export the exec node and paste it here? Change any sensitive IDs!
Paste as code using the </> button not as a screen capture.

Topic		Replies	Views
Exec node - help with how it spawns General	15	470	13 March 2025
Exec node is not responding General	27	1260	4 May 2022
Exec node - piping payload to stdin for commands General	31	374	14 December 2024
Problem with exec node output in Spawn mode General	25	577	16 February 2023
Exec node timeout not working in 'exec' mode General	34	3608	9 August 2020

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Exec-Node: Works fine in Linux Terminal, but not in Exec-Node

Related topics