Using CATT

Thanks!! It works!!

work for me! thanks!

4 Likes

Does anyone have a guide to use ssh instead of stdin?

1 Like

This would be helpful. I haven’t updated the Terminal add-on b/c I rely on the addon.stdin for several automations.

This is probably unrelated but I wanted to share it to see if anyone else has seen it.

Yesterday I saw a Welcome to Home Assistant splash screen appear on one of my Google Home Hubs.
It was full screen and included the HA logo and blue background.

I was in a hurry heading out the door so didn’t get to touch the screen to see if there was any interaction.

Has anyone else seen this and if so what is it?

CATT via ssh works exactly as described by Lesley.
only one little typo :wink: ssh-keygen -t rsa
Config for SSH Terminal should look somehow like

init_commands:
  - python3 -m pip install catt==0.12.2
packages: []
share_sessions: false
ssh:
  allow_agent_forwarding: false
  allow_remote_port_forwarding: false
  allow_tcp_forwarding: false
  authorized_keys:
    - >-
      ssh-rsa     
      AAAAB3NzaC1y..........****yourKey**********........

and same as using stdin
always use stop command before starting new cast in automation

Big Thanks to Lesley

1 Like

Hi, i have got CATT auto installing now using your above code (Thank you), do you or anyone here know how i can automate the cast, since the latest version of SSH doesn’t support the old method ( Using CATT - #492 by thehijacker )

Has the CATT 30 second display on a V1 hub problem been resolved ?
Using terminal, I am able to CATT to my V1, but it disappears after 30 seconds. My V2 hub will display the CATT 10 minutes. Then I issue a STOP then I can re-CATT.

@Luitertje I am working on your SSH method of creating a switch. Testing in terminal but it is asking for a password. No passwords I have tried have worked. I think it wants the id_rsa.pub key. How can I copy/paste the key into Terminal ? I used CTRL-right click-paste the id_rsa.pub key but it still has permission denied.

SOLVED: My issue was that the username&password should have been the username that is set up in the SSH&Web add-on and NOT one of the HA usernames

Hi Braindrian,
the purpose of a ssh key means that you don’t have to use a password actually. You did create the key right? Where did you store it? Also did you put the content of the public key (id_rsa.pub) in the configuration of the ssh add-on? Furthermore make sure that the /config/ssh/id_rsa in the code is the right path to where your id_rsa lives.

1 Like

Thanks for the reply.
You mentioned testing the key with a login. Could you explain how I would do that?
When we generate the key-pair does it get associated with a specific user account? I will test logging in with Putty and the key.

I stored the keys in a folder /config/ssh.

init_commands doesn’t work, what do I use now? I don’t see anything in the ssh addon documentation for init_commands, is it a modified addon?

Did you try the init_commands in this post? That one worked with my terminal addon.

python3 is removed every time the ssh addon restarts. I am unable to use init_commands at all and I am wondering if it got renamed to something else.

This is my current config. None of the commands execute automatically aside from server params.

init_commands:
  - apk add build-base
  - apk add py3-wheel
  - apk add py3-pip
  - python3 -m pip install catt
server:
  tcp_forwarding: false
  allow_agent_forwarding: false
  allow_remote_port_forwarding: false
  allow_tcp_forwarding: false

I want to add that I am on a Raspberry Pi.

What happens if when you run these commands after loading terminal ? I am assuming you have a Github account.

Also, there are 2 SSH add-ons. Make sure you use the SSH & Web Terminal not the Terminal & SSH add-on.

Try these commands in the terminal window
python3 -m pip install catt
or
catt scan

Edit:
I found this in the documentation for SSH & Web Terminal:

Option: init_commands

Customize your shell environment even more with the init_commands option. Add one or more shell commands to the list, and they will be executed every single time this add-on starts.

So the Init command re-installs a fresh copy of CATT each time you restart HA.

Alright, thanks, I ended up giving up on CATT after figuring out the 30 second bug. Hopefully it gets fixed at some point.

I think the regular HA Cast integration allows constant connection. I have heard the transitions between pages is quite awkward and some cards do not work. CATT worked very well, all of my cards worked but unfortunately it has been updated to death.

I have 2 hubs and only one a V1 has the 30 second issue so far. I had though there was a work around for this so it might be worth posing the question again as I did in post number 495. Which version do you have ?

I have the V1 and got the 30 seconds bug…

Do we have a work around for the 30 second bug ?