Newbie, how to add an external component?

yellow.apple · May 13, 2019, 3:20pm

Hello, thank you for your time. ssh_axel.sh is launching an SSH command to the Ubuntu host.

#!/bin/bash
ssh [email protected] /usr/share/hassio/homeassistant/scripts/quota_axel.sh

I get this in the log at the exact command line.

[homeassistant.components.hassio] Invalid config for [shell_command]: invalid slug Quota_axel (try quota_axel) for dictionary value @ data[‘shell_command’]. Got OrderedDict([(‘Quota_axel’, ‘/bin/bash scripts/ssh_axel.sh’)]). (See /config/configuration.yaml, line 46). Please check the docs at https://home-assistant.io/components/shell_command/

Changed yaml configuration to the Following, no more error message. I’ll try to copy the ssh_ID the local config folder.

shell_command:
quota_axel: /bin/bash scripts/ssh_axel.sh

yellow.apple · May 13, 2019, 3:32pm

quota_axel.sh is an expect script shutting down a port on a Cisco switch. At the end it should reset a user quota on a Fortinet firewall. The main goal is to give internet access back.

flamingm0e · May 13, 2019, 3:36pm

Is this the entirety of the script? If so, you don’t need to create a .sh and call it, you can put that one line command in the shell_command

Also, your IP address…use the LAN IP and not the docker IP.

Can you please format your code properly and post it?

This is very telling

yellow.apple · May 13, 2019, 3:41pm

The problem is that quota_axel.sh is an expect script not supported in docker.
Here is the script, quite simple

quota_axel.sh

#!/usr/bin/expect -f
set timeout 5
set IPaddress “192.168.1.240”
set Username “cisco”
set Password “cisco”
set Status “shut”
set Port “G15”
spawn ssh -o “StrictHostKeyChecking no” $IPaddress
expect “User Name:”
send “$Username\n”
expect “*assword:”
send “$Password\n”
expect “#”
send “conf t\r”
expect “(config)#”
send “int $Port\r”
expect “(config-if)#”
send “$Status\r”
expect “(config-if)#”
send “exit\r”
expect “(config)#”
send “exit\r”
expect “#”
send “wr mem\r”
expect “#”
send “exit\r”
sleep 1
exit

From the HA console.

flamingm0e · May 13, 2019, 3:56pm

I guess I haven’t been clear enough. It doesn’t NEED to be supported in Docker.

Literally, this is the command I am telling you to use DIRECTLY in the component for the shell_command. For whatever reason, you created a script that does what I am telling you to put IN the shell_command line.

ssh [email protected] /usr/share/hassio/homeassistant/scripts/quota_axel.sh

This command runs it on ANOTHER machine (in this case, the HOST OS, and has NOTHING to do with Docker)

yellow.apple · May 13, 2019, 4:00pm

I’ve used SSH as you have explained to launch an Expect script on the host Ubuntu because this is not supported in Docker and this is working fine.

Now I understand that the local script is not mandatory but It should work !!! The local script is also helping me to test the command inside docker.

Here is the new configuration.yaml but this is the same issue, no entities and no more logs
I’ve changed the name to match the Cisco script. (Port shutdown)

Even this one is not working….

flamingm0e · May 13, 2019, 4:37pm

How is it helping you do that?

You added those, and then restarted home assistant?

I have said it a few times already, but stop using the DOCKER IP address for your host, and use the host IP address. PLEASE! For testing sake!

yellow.apple · May 13, 2019, 5:14pm

This is helping to avoid typo issue and yes of course I’ve restarted HA.

Concerning your last remark, 172.30.32.1 is the Ubuntu address (First host) on the same subnet as of the Docker 172.30.33.4/23. I’m always using close IP addresses to avoid routing or nating issues. I’m newbie ONLY in home assitant !!

The command is of course working perfectly in the docker shell with the two IP addresses of the Ubuntu. The picture that I’ve posted 1h ago with the script and the result in the console is the perfect test !

Finally, If you have looked carefully at my last “configuration.yaml” extract, I’m simply asking for an “ls” command. The following line is in comment !!

flamingm0e · May 13, 2019, 6:05pm

you’re asking for ls INSIDE the docker container.

What are you expecting to happen after it does that? Are you expecting some entity to show up on the frontend?

What does this mean?

What do you expect to be in the entities list?

DavidFW1960 · May 13, 2019, 10:15pm

The 172.30.x.x is a DOCKER IP address, not the IP address of the host which is what you should be using. What is the real IP address of the Ubuntu machine? What does your router allocate to it? That is what you need to use.

yellow.apple · May 15, 2019, 6:06pm

For the networking part: 172.30.32.1/23 is the subnet dedicated to the Ubuntu/Docker communication which means that on that specific subnet I currently have two IP addresses.

The Ubuntu server 172.30.32.1/23 (GW)
The HA docker 172.30.33.0/23 (DHCP)
I can also reach the internal IP address of the Ubuntu server, in my case 192.168.1.245 but I would not recommand it for internal communications. (SSH between the two!)

Here is now what I have on my PI touch screen. I still have to find how to update the status because one of the two should be green ON.

For that I’ve created entries in the scripts.yaml

stop_wifi:
sequence:
- service: shell_command.stop_wifi
start_wifi:
sequence:
- service: shell_command.start_wifi

With the lines above, I have new automatic entries in the “entities tab”

Finally the SSH issue was coming from the local location of the id_rsa key.
Here are the working commands in the configuration.yaml file.

shell_command:
stop_wifi: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /config/.ssh/id_rsa [email protected] /usr/share/hassio/homeassistant/scripts/expect_stopwifi.sh
start_wifi: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /config/.ssh/id_rsa [email protected] /usr/share/hassio/homeassistant/scripts/expect_startwifi.sh

Thank you for your help.