What does that even mean?
Plugs can be minimised.
It should look like
or better
With “invisible cable at the back” and no* plug on one side, etc.
Reqarding plug, this lenovo is somehow o.k.
but it is too big, the stand is too much stand (see bottom) and the device too much a tablet and it is black.
Perhaps I missed devices in my long search trips, which you have in mind. So I would appreciate having your advice: max 6 inch, white, no visible plug, integrated or seamless stand.
no thoughts but same issue here since today 
Yes, same issue here as of today. Not sure when/if my nest hub max had a firmware update though…
I’m on 1.56…265669, which isn’t even listed on the firmware website.
Certainly different to the 30s issue I had on the nest hub after firmware update. This time it won’t even cast at all. I run the command, and command line basically freezes.
Same on nest hub 2.
Terminal freezes after running cast site command.
It seems that the cast stream does not get disconnected after the 10min timeout and CATT refuses to connect again.
Add “catt -d “your_device” stop” to your reload script to stop the cast stream before reloading.
if ! catt -d “your_device” status | grep ‘PLAYING’; then
catt -d “your_device” volume 0
catt -d “your_device” stop
catt -d “your_device” cast_site http://xxx
fi
1 Like
Awsome!
Back in service.
Thanks
Now looking forward for the next update surprise 
Legend. Yeah, I should have realized that, as after I manually stopped the cast from the home app it worked initially, and then failed. But it didn’t twig that that was the issue!
Reading your solution you don’t have the 30 second issue. Are you not casting to a nest hub?
If you are what are the firmware versions on your device?
Im not having the 30sec issue yet.
Casting to a nest hub with firmware 1.56.265669
also tried this on my Hub 2 (fw 1.56.265669) but without any result 
Also restarted by Hub and HA but still no luck…hope to get a fix soon!
Strange… If you issue the stop command manually after timeout, does the cast site command work?
Is the cast stream still active i the GH app after timeout?
whoops…sorry, my mistake! 
It works after I installed CATT again.
So, is it normal behaviour that CATT needs to be reinstalled after rebooting HASS ?
Previously I used to run HASS in a container where I didn’t notice this issue, but since some weeks I have a HA Blue 
Yes CATT needs to be reinstalled. I have a automation that (re)installs CATT with the “HA started” trigger incase of a reboot or power loss.
Good idea!
I tried to create an automation to install catt in HA start, but for some reason it doesn’t install CATT.
My code:
alias: Install CATT on Boot
description: ''
trigger:
- platform: homeassistant
event: start
condition: []
action:
- service: hassio.addon_stdin
data:
addon: a0d7b954_ssh
input: bash pip3 install catt
mode: single
Do you might sharing your automation to see what’s wrong with mine ?
Thanks!
You don’t need an automation to install on boot. Just add an init_command to your ssh & web terminal add on configuration. I have it to install a specific version, as I had some issues that I’m not sure are resolved.
init_commands:
- python3 -m pip install catt==0.11.3
2 Likes
Thanks, but does not seem to work for me
For anyone experiencing the 30s timeout issue on their nest hub. I have created a forum topic to request the timeout get increased on the nest hub community for you to add your support for visibility.
2 Likes
Got the same firmware, but no luck…I’ve restarted my hub2, home assistant…re-installed SSH&webterminal, re-installed catt
if ! catt -d “Woonkamer” status | grep ‘PLAYING’; then
catt -d “Woonkamer” volume 0
catt -d “Woonkamer” stop
catt -d “Woonkamer” cast_site http://192.168.1.9:8123/lovelace/home
fi
something wrong in here? it’s the only thing that has changed…
Hope you can help me out
How do the manual commands react when running via terminal?
-
catt -d “Woonkamer” stop
-
catt -d “Woonkamer” cast_site http://192.168.1.9:8123/lovelace/home