Using CATT

Configuration
99

yes, i’ve used the internal url:
https://192.168.1.xx:8123/lovelace/0
but the Nest hub gets stuck on the dashcast screen. Says “force loading: https://192.168.1.xx:8123/lovelace/0”
i’ve only one user ( with the exception of users automatically generated by the homeassistant system)
i’ve changed the theme to default white but the cast keeps the black theme…
PS: i’m on Raspberry Pi4 with rasbian lite and hassio installed trought docker

100

Do you use https? Try using http as it’s your internal network.

And no need to anominize your internal IP, nobody here is able to reach that :slight_smile:

101

LOL it’s a paranoid thing u r right!
if i use http i can’t reach the server with hassio,
could it be due to duckdns? I forwarded the ports on the router from 8123 to 443 and i can reach the hassio at https://xxx…duckdns.org/lovelace/0 without problems, if through a browser, I try to connect to http://192.168.1.12:8123 (yes yes this is the hassio internal IP I confess :wink: ) the browser says: ERR_EMPTY_RESPONSE

1 Like
103

I’m trying to use CATT but it keeps asking for a username and password on the google home hub, I’ve added auth providers to my config as below, not sure where else to go?

homeassistant:
  auth_providers:
   - type: homeassistant
   - type: trusted_networks
     trusted_networks:
       - 127.0.0.1
       - 192.168.68.0/24
     allow_bypass_login: true
104

Can you check my earlier comment here to see if that solves it for you as well?

105

Thanks for this, this is the screen I see and I’ve tried clicking under the password field but can’t get trusted users to appear? image
Just to add I get this notification in home assistant also

Login attempt or request with invalid authentication from 192.168.68.108

106

It’s even below the Next button (pushing that one gives the authentication message in the log).
The field is not visible, probably caused by the dark theme. See the picture below, you have to press on the position of Trusted Networks on your hub.

image
image828×990 111 KB

3 Likes
107

Got it! Thanks for this! Must have pressed ever bit of the screen apart from this but when I tried before! Now to add to a command line switch!

108

Would anyone be able to help with an issue? I’ve got CATT working fine if I use the command in a terminal window but looking to trigger as part of a script. I’ve tried to follow the example above and it says the script is triggered but no response.
The shell command I’ve used is

shell_command:
  cast_kitchen_display: ssh -i /config/ssh/id_rsa -o StrictHostKeyChecking=no [email protected] "/home/matt/.local/bin/catt -d 'Kitchen Display' cast_site 'http://192.168.68.110:8123/lovelace-system/system-info'"

Home Assistant is running on the same host as catt if that makes a difference in the IPs I use. I also have passwords disabled on the host and only access via ssh key again if that makes a difference to the command? I only have one chrome cast as well so should I remove -d Kitchen Display? Should it literally just be catt cast_site command?

109

Only thing I have different in mine is -o "StrictHostKeyChecking=no" but looking at other posts on here that doesn’t seem necessary. Might suggest trying something simple like this to see if SSH is even working:

ssh -i /config/ssh/id_rsa -o StrictHostKeyChecking=no [email protected] ping 192.168.68.110
110

I wanted to thank folks for this thread as I’ve found CATT to be infinitely more reliable than HomeAssistant Cast. I wrote a blog post laying out how to get CATT set up, let me know if you folks think I missed anything: https://blog.fuzzymistborn.com/homeassistant-and-catt-cast-all-the-things/

4 Likes
111

How do you authorise when you just want to cast to a chromecast attached to a TV, which has no touch capabilities?

112

I could not make it work either. I made it work using node red with a node “bigssh” and the command : catt -d IPADRESS cast_site ‘https://xxx:8123/lovelace/home’
This command is triggered by the state of input boolean. HA then changes this input boolean via script

113

Guess you can’t if there’s no touch capabilities.

114

Thanks, I’ve got it working with the following

ssh [email protected] "/home/matt/.local/bin/catt -d 'Kitchen Display' cast_site 'http://192.168.68.110:8123/lovelace-system/system-info'"

Think the issue was ssh keys and the port

I’ve added this as a shell command in my config and then to a script but it doesnt seem to work in that the script fires but nothing happens on my Google Hub but if I use the command in the terminal in HA it does work. Should I use a command line switch instead?

115

Thanks, I managed to get it partially working as above, when you say you couldnt get it to work, was it with the script as I am struggling on this or was it the command in general?

116

It was with the shell command in home assistant. It worked always ok with the commande in the terminal

117

Ah that’s the issue I seem to be having now…

118

Yeah use shell_command and call it as a service. I have an example in my blog post.

119

Are you using ssh keys with bigssh?