Shell_command / ssh: return_code 255

[prankousky]

Hi everybody,

I have this shell script below, that I can successfully run when I ssh into my hassos; it will work as intended, in this case, toggling audio playback on a remote linux machine.

However, when I run it through shell_command, I only get Error running command: /config/packages/cli_helper.sh "toggle_playback", return code: 255 , What do I need to change in order to make this work?

cli_helper.sh

#!/usr/bin/env bash

HOST="10.10.2.22"
USER="me"

ssh -i /root/config/security/hassos $USER@$HOST "/home/me/bin/ssh_geruest.py" "$1"

# vi: ft=bash

yaml

shell_command:
  unten_arbeitszimmer_drehknopf_toggle_playback: /config/packages/cli_helper.sh "toggle_playback"

---

EDIT: I also had it like this unten_arbeitszimmer_drehknopf_toggle_playback: '/config/packages/cli_helper.sh "toggle_playback"', no difference.

---

Again, I positively can ssh into my machine and run this; so both the identity file and the code itself must be correct. I ssh into hassos, run this code, and audio playback will toggle on my desktop PC.

I try running this through Home Assistant itself, and I get the error above. I have this in my configuration.yaml

allowlist_external_dirs:
  - "/config/security"

This directory seems to work fine as well; Home Assistant can write to it (via camera.snapshot) and access the files there (via notify.telegram).

These are the contents of that directory; it’s permission seem to be correct as well.

What am I missing? Thank you in advance for your help

[wmaker (Tommy Long)]

Here is a link you might find helpful

SSH'ing from a command line sensor or shell command

I’ve noticed there’s a significant number of posts looking for help on this topic and the posters all seem to struggle with a few common issues. I realized I’ve been almost copying and pasting my responses on these topics so it seemed like a good case for a community guide. What will this cover This guide will walk through the process of getting a command which ssh’s into another machine to get some simple data ready to be included in a command line sensor. To keep it simple I’ll use the same …

A couple of thoughts:

• When you run it manually to see if it works, make sure you do so inside the homeassistant container and note that its config path is /config.
• Follow the guide, as you’ll need an ssh option to deal with the fingerprint reply from the remote host

[prankousky]

Thank you. I had to add -o UserKnownHostsFile=... to my bash script. Now it works fine, after copying the known_hosts file to my packages directory and pointing to it.

[wreckshop (Mo)]

@SSH'ing from a command line sensor or shell command

-o UserKnownHostsFile=/config/.ssh/known_hosts

Swinging through two years later to say you’re my hero.

I was at this for a hilarious amount of time. Tragically, I had EVERYTHING handled just fine (keys, ssh, proper config path, ssh, .ssh, etc) and I was certain the container was the issue, but at no point did anyone in any forum - nor did anyone include in any official documentation that I combed through - either of

1. the “protection mode” setting, or
2. the docker exec -it homeassistant bash command

Home Assistant container did indeed just need the ol’ fingerprint/yes/green light/high five/karate chop.

As a serious shell script and workflow junkie who automates even the silliest things, thank you very much!