One Chromecast does not respond despite being scanned.

[SpiraFax]

trafficstars

I have 4 chromecasts all of the same type. when I "catt scan" it finds all 4 devices. three of them can command but the 4th says "Error: no device found at <IP>".

I can ping said IP and command through other methods.

I have been using catt for about a year commanding this chromecast without issue. I have not use it to command others much.

I apt upgraded everything on my system and now it has stopped working.

I have upgraded catt to the latest through pip3 but still no luck.

is there some kind of lock file or cache file to clear?

[theychx]

Could you post the output of catt scan?

[SpiraFax]

Thank you for the quick response.

> ➜  ~ catt scan                   
> Scanning Chromecasts...
> 192.168.1.234 - Bedroom TV - Google Inc. Chromecast
> 192.168.1.235 - Gym TV - Google Inc. Chromecast
> 192.168.1.236 - Living Room TV - Google Inc. Chromecast
> 192.168.1.237 - Office TV - Google Inc. Chromecast
> ➜  ~ catt -d 192.168.1.237 status
> Error: No device found at 192.168.1.237.
> ➜  ~ catt -d 192.168.1.236 status
> Volume: 44
> ➜  ~ catt -d 192.168.1.235 status
> Volume: 100
> ➜  ~ catt -d 192.168.1.234 status 
> Volume: 100
> ➜  ~ catt -d 192.168.1.237 status
> Error: No device found at 192.168.1.237.

[theychx]

Can you reach it with catt -d "Office TV" status?

Also, you should install catt with pipx these days, there's been some breakage lately with zeroconf.

[SpiraFax]

similar result (also "office" is in my config)

➜  ~ catt -d "Office TV" status
Error: Specified device "Office TV" not found.
➜  ~ 
➜  ~ catt -d office status   
Error: No device found at 192.168.1.237.
➜  ~ 

[SpiraFax]

update: I have reinstalled catt with pipx with the same result.

I have also tried on a different machine. which leads me to think that it is not a conflict with a previous version.

[SpiraFax]

update: the problem remains to only be an issue with CATT. using my android phone, use home assistant integration and go-chromecast all work fine with the CC in question but the problem with CATT has been intermittent.

[theychx]

Hmm, strange. I can't reproduce this, I'm afraid.

[FlexxFR]

Hmmm.. just created a similar issue while now reading this one. I have it with Google Hub instead of Chromecasts In my case only a reboot of the device solves it for a while. Don't know how a device end up in the "half-working" state (=working normal but CATT is not).

I noticed the such a device is also not configurable anymore via the Goolge Home app but you can still operate it (for example volume control, screen mirroring/casting). The configure (gear) icon is gone. After reboot it's back....????

I'm not sure if CATT is the cause to "hang" the Hub or it's the other way around. Did you even figured this out?

[skorokithakis]

I can sometimes reproduce this, but it seems to be a Chromecast error rather than a catt error, because when it happens none of my devices can see the Chromecast.

[FlexxFR]

But when this happens, Catt scan does still detect the device. (or is that cached?) Af fresh scan still lists the device while I can't send any commands.

[skorokithakis]

Hmm, then I don't have the same issue as you, I think.

[FlexxFR]

I'm just figured out I'm running a very new firmware version, 1.56. Maybe a new "feature"? (BTW, did not encounter the 30 sec time-out issue with this version)

[finndev]

I am experiencing the same issue, output of catt scan:

$ catt scan
Scanning Chromecasts...
172.16.0.34 - 65OLED855/12 - Google Inc. TPM191E
172.16.0.74 - Friseur  TV - Google Inc. Chromecast
172.16.0.252 - Friseur TV - Google Inc. Chromecast

and then the following error appears when casting a website:

Error: No device found at 172.16.0.74.

The device is pingable and up and running (displaying the default Chromecast wallpaper).

64 bytes from 172.16.0.74: icmp_seq=2 ttl=64 time=1.53 ms

This usually happens every 24-48hrs. We are using catt to cast a price list to a screen in a barbier shop.

If anyone has any tips on how to resolve it, I would love to hear it.

[FlexxFR]

I "solved" it by doing two things at the same time, so actually I don't know which of them really helped or both are needed.

1. Updates all my ubiquity network stuff, created a 2.4Ghz wlan and joined the Google device to that SSID. I want to made sure the device was forced to connect to the nearest access point.
2. I run CATT as proxmox container. So I created another one and used cron to do a catt scan and catt info on the troublesome device every 10minutes. I wrote the out to a logfile with the intension to do some troubleshooting (like when it stops).

However, after these changes it works 100% solid....never looked at the logs again. (This reminds me that somewhere on my server a log is still being filled..... ;) )

[finndev]

We also use Ubiquity, so I thought creating the 2.4 Ghz wlan and pin the Chromecasts to a specific AP would fix the issue. Unfortunately it did not. I have upgraded all packages + catt, and we use the cast_site functionality. After 24-48hrs the Chromecasts just go back to the wallpapers and catt is unable to access the devices again. It can scan them, but not access them.

Scanning Chromecasts...
172.16.0.34 - 65OLED855/12 - Google Inc. TPM191E
172.16.0.74 - TV outside - Google Inc. Chromecast
172.16.0.252 - TV inside - Google Inc. Chromecast
Casting...
Error: No device found at 172.16.0.74.
Error: No device found at 172.16.0.252.

And some more logs:

$:/home/pi# catt -d 172.16.0.74 status
Error: No device found at 172.16.0.74.

$:/home/pi# telnet 172.16.0.74 8009
Trying 172.16.0.74...
Connected to 172.16.0.74.
Escape character is '^]'.

$ catt -d 172.16.0.74 info
[(172.16.0.74):8009] Failed to connect, retrying in 5.0s
[(172.16.0.74):8009] Failed to connect. No retries.