Chromecast Integration (beta) severe lag

🧰 Built-In Apps and Drivers Built-in Apps
1

Hi folks, I can't seem to figure out what could be causing this and can't get the logs to show anything valuable that would point to why there is a severe delay when sending a speak command to multiple nest minis/hubs either by selecting each of them or by using a group created in Google Home and shared with Chromecast integration.

The physical behaviour is that it seems to initiate the message with all the relevant speakers as you hear the ping sound, then you have to wait anywhere from 2 mins up to 4 mins for it to actually play the message, sometimes it doesn't even bother. There are no time out messages in the logs i can see, no delays, nothing that relates to this?

Any ideas?

Currently running version: 2.2.8.156

Thanks, Alan.

2

Ok, so after restarting and forcing a few diff test rules to try and get some feedback the hub started to slow down and not respond to web requests but here is what it posted to the logs....

app:1522021-08-26 15:08:52.206 warnmethod appButtonHandler of child app TestVolume ran for 307,002ms

dev:32021-08-26 15:08:51.114 infoNestMiniToyRoom media source is Hubitat

dev:1622021-08-26 15:08:50.459 errororg.codehaus.groovy.runtime.InvokerInvocationException: su.litvak.chromecast.api.v2.ChromeCastException: No application is running in ChromeCast (method runQ)

dev:1622021-08-26 15:08:50.341 warnmethod setVolume of device All Devices ran for 319,959ms

dev:1622021-08-26 15:08:50.188 warnmethod setVolume of device All Devices ran for 304,935ms

dev:52021-08-26 15:08:49.691 errororg.codehaus.groovy.runtime.InvokerInvocationException: su.litvak.chromecast.api.v2.ChromeCastException: Waiting for response timed out (method parse)

dev:412021-08-26 15:07:48.393 warnmethod parse of device NestMiniLivingRoom ran for 313,962ms

dev:412021-08-26 15:07:48.388 infoNestMiniLivingRoom media source is None

dev:62021-08-26 15:07:35.571 infoNestMiniMasterBedroom media source is None

dev:392021-08-26 15:07:35.544 infoNestMiniBackRoom media source is None

dev:82021-08-26 15:07:35.535 infoNestMiniGroundFloorBathroom media source is None

dev:22021-08-26 15:07:35.517 infoNestMiniKitchen media source is None

dev:72021-08-26 15:07:35.449 infoNestMiniEnSuite media source is None

dev:42021-08-26 15:07:35.439 infoNestMiniLanding media source is None

dev:32021-08-26 15:07:35.430 infoNestMiniToyRoom media source is None

dev:52021-08-26 15:07:35.370 infoNestMaxKitchen media source is Default Remote Control CAF

dev:1532021-08-26 15:07:17.090 errororg.codehaus.groovy.runtime.InvokerInvocationException: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe (Write failed) (method parse)
dev:52021-08-26 15:03:36.639 errororg.codehaus.groovy.runtime.InvokerInvocationException: su.litvak.chromecast.api.v2.ChromeCastException: Waiting for response timed out (method parse)

3

app:1522021-08-26 15:13:08.480 warnmethod appButtonHandler of child app TestVolume ran for 578,194ms

app:1522021-08-26 15:13:08.328 warnmethod appButtonHandler of child app TestVolume ran for 525,780ms

4

Maybe this is the same issue. If it is looks like a fix is coming.

Tagging @gopher.ny just in case it is a different issue.

1 Like
5

Thanks @bobbles, it may be the same, but hopefully a solution can be found soon as that thread was logged 5 weeks ago and its pretty much rendered 60% of my automations useless :frowning:
Just wondering why it hasn't affected more users by now, but maybe not enough folk have upgraded to the latest software.
Thanks.

1 Like
6

I'm at the latest build and have 2 speakers integrated.
I only use one for announcements and it is working OK.
Maybe it's something to do with the number of devices.

As a matter of interest this integration gave me mega hub issues around 2 years ago. It was Beta then and it still is!!!!!
Not sure if this is a low priority integration.

7

I'm on the latest build and have 6 of my 8 devices integrated. I'm not experiencing this delay. My devices announce in a timely fashion. I have seen up to a 2 second delay on occasion but this has always been the case for me. My 2 nest hubs are running fuchsia (sp?).

I did try using the polling option that was recently introduced and found it didn't work for me. I had to restart my RM rule that refreshes/initializes each device every 4 minutes.

8

That's a good point that I completely forgot about.
I'm using @bptworld's Chromecast Helper to initialise my devices every 4 minutes.
Not sure if this is doing the trick or not.

Just search for 'chromecast' in HPM to download it if you are not using it and want to give it a try.

9

Thanks, trying that now, I hadn't even got HPM installed so have installed it now too. Will report back later if it makes a difference.

1 Like
10

No joy I'm afraid, still the same outcome with using Chromecast helper set to 4 min refresh. Hopefully a fix is due soon. Thanks for your assistance and ideas.

1 Like
11

Been having the same issue for some time. Sometimes, it's several minutes between an action and the speech. I removed Chromecast Helper a couple months ago, or so, as I had read it was unnecessary with the HE update.

12

Same issue. Which is Not great as I use it for leak detection...

13

I reinstalled Chromecast Helper. It seems to be working normally, thus far. It's only been a day or two.