Shell Command not working in Automation

[rcrail (Richard Crail)]

I am trying to assure a Sony Bravia TV is using its speakers rather than audio system prior to starting an automation action. The REST example came from: https://github.com/home-assistant/core/issues/88532 which was used to create a shell command that was added to configuration.yaml as:

#Exposes shell_command,sonytv_speakers shell_command: sonytv_speakers: curl -X POST \ http://xxx.xx.xx.xxx/sony/audio \ -H 'cache-control:no-cache' \ -H 'x-auth-psk:xxxx' \ -d '{"method":"setSoundSettings", "id":5, "params":[{"settings":[{"value":"speaker", "target":"outputTerminal"}]}], "version":"1.1"}'

The command works when entered directly in the terminal and there are no errors in the configuration.yaml file. (“xxxxxxxx” used in lieu of actual IP and PSK.)

However when envoked as a service call in an automation, for example:

action: shell_command.sonytv_speakers data: {}

nothing happens and the log error is:

``Logger: homeassistant.components.shell_command
Source: /usr/src/homeassistant/homeassistant/components/shell_command/init.py:129
integration: Shell Command (documentation, issues)
First occurred: 5:30:04 PM (1 occurrences)
Last logged: 5:30:04 PM

Error running command: curl -X POST \ http://xxx.xx.xx.xxx/sony/audio \ -H 'cache-control:no-cache' \ -H 'x-auth-psk:xxxx' \ -d '{"method":"setSoundSettings", "id":5, "params":[{"settings":[{"value":"speaker", "target":"outputTerminal"}]}], "version":"1.1"}', return code: 3
NoneType: None``

I would appreciate suggestions to make the automation work as planned.

[esand (Eli Sand)]

If the return code from curl was 3, supposedly that means the URL was malformed. Check that you’re properly escaping your command line in YAML maybe?

[tom_l]

It is not clear what you are doing from your poorly formatted post. But…

You can’t define shell commands directly in your automation.

You need to save the shell command first using this:

Shell Command

Then call that shell command in your automation.

Please take note of this:

There’s a community guide that may help if this is your issue: SSH'ing from a command line sensor or shell command

[dbs (David)]

Sometimes the version of the command is not what you’re expecting. I have often had to create a shell command just to find the version of the command (e.g., which version of curl you have installed) so I can make sure it supports what I’m doing. If you’ve got simple curl commands working but complex ones don’t, check the version!