shell_command variables not working after 2025.2.0 update

[pickonedev]

The problem

Hi!

I have this situation:

a shell_command:
tablets_adb_pair: adb pair {{argument1}}:{{argument2}} {{argument3}}

a script:

action: shell_command.tablets_adb_pair
metadata: {}
data:
  argument1: "{{ states('sensor.tablets_ip_select') }}"
  argument2: "{{ states('input_text.tablets_adb_pair_port') }}"
  argument3: "{{ states('input_text.tablets_adb_pair_code') }}"

an automation which runs the script after all the values from the arguments, are valid.

Before 2025.2.0 this was working flawless, now, I get this into the logs and no functionality...

Logger: homeassistant.components.shell_command
Source: /usr/src/homeassistant/homeassistant/components/shell_command/__init__.py:129
integration: Shell Command ([documentation](https://www.home-assistant.io/integrations/shell_command), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+shell_command%22))
First occurred: 11:52:42 (1 occurrences)
Last logged: 11:52:42
Error running command: `adb pair {{argument1}}:{{argument2}} {{argument3}}`, return code: 1

NoneType: None

What version of Home Assistant Core has the issue?

core-2025.2.0

What was the last working version of Home Assistant Core?

core-2025.1.x (as far as I remeber, but could be around 2024.x.x)

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (shell_command) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of shell_command can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign shell_command Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

shell_command documentation
shell_command source
_{^{(message by IssueLinks)}}

[abmantis]

If you ran the shell_command.tablets_adb_pair using the Developer tools does it also fail?
What if you use static values (instead of templates)?

[pickonedev]

Yes, this is the output from developer tools

stdout: ""
stderr: "error: protocol fault (couldn't read status message): No error information"
returncode: 1

And this is from logs

Logger: homeassistant.components.shell_command
Source: /usr/src/homeassistant/homeassistant/components/shell_command/__init__.py:129
integration: Shell Command ([documentation](https://www.home-assistant.io/integrations/shell_command), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+shell_command%22))
First occurred: 11:52:42 (2 occurrences)
Last logged: 23:27:37
Error running command: `adb pair {{argument1}}:{{argument2}} {{argument3}}`, return code: 1

NoneType: None

[peter-dolkens]

Same issue here

Logger: homeassistant.components.shell_command
Source: /usr/src/homeassistant/homeassistant/components/shell_command/__init__.py:129
integration: Shell Command ([documentation](https://www.home-assistant.io/integrations/shell_command), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+shell_command%22))
First occurred: February 16, 2025 at 7:12:43 PM (7 occurrences)
Last logged: February 16, 2025 at 11:47:46 PM
Error running command: `ssh -i /config/.ssh/id_rsa -o UserKnownHostsFile=/config/.ssh/known_hosts peter.dolkens@nas.local 'sudo /sbin/poweroff &'`, return code: 255

NoneType: None

- platform: wake_on_lan
  name: nas_wol_1
  mac: '00:xx:xx:xx:xx:xx'
  host: 'xxx.xxx.xxx.240'
  turn_off:
    service: shell_command.nas_shutdown
   

nas_shutdown: ssh -i /config/.ssh/id_rsa -o UserKnownHostsFile=/config/.ssh/known_hosts peter.dolkens@nas.local 'sudo /sbin/poweroff &'

[abmantis]

return code: 255

@peter-dolkens it seems that the command was ran, but returned an error. Does not seem like an issue with the shell_command itself.

[cefoster0]

same error here. pre-existing automations can execute the shell commands, but nothing shows up in the GUI as actions either in dev tools or automation editing. searching for 'shell command' in the dev tools actions does not show up.

[pickonedev]

Updated to 2025.2.4, still not working :-(

Till shell_command will work again, I managed to use this custom add-on https://github.com/zhbjsh/homeassistant-ssh

[josiahls]

Looks like 2025.4.2 works, and in the visual editor, you see the response variable field which wasn't there before.

Also lolled at @pickonedev doing adb stuff. I thought I was special in trying to use adb to automate my phone.

[jkosharek]

Running 2025.4.3 and shell_command with variables is still broken. :(

[petos]

I actually lost the "shell_command" at all:

shell_command: 
    test: touch ~/test.txt

But I'm getting error in gui:

Action button.press uses action shell_command.test which was not found.

In logs:

Kamera zahrada vlevo press: Error executing script. Service not found for call_service at pos 1: Action shell_command.test not found

Any hint there?

Core 2025.5.2
Supervisor 2025.05.1
Operating System 15.2
Frontend 20250509.0

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.