Chrome cast tts quit working

🛎️ Get Help Integrations
2

Is nobody else having this problem?

3

Reverted my firmware back to .130. It works fine now. So definitely something in the latest firmware. Not sure who to tag. @gopher.ny

4

I’m seeing the exact same thing. Reverted back to previous version and everything is working again too.
Glad I’m not the only one.

5

Exact same issue here. I'm new though on HA (just moved from ST), but is having a lot of issues with Chromecast Integration. Works on/off, but after update today to .132 everything is just dead with "java.util.concurrent.TimeoutException: Execution timed out after 45 units. Start time: Sun Jan 15 17:45:27 CET 2023 on line 232 (method runQ)"

6

Sure glad to hear it isn’t just me. @bravenel

7

Yep and same here. Chromecast "casting" is not working.

8

Is everyone using "TTS Delay enable"? When I turn that on, even sending a set volume command causes this error. When I disable the TTS delay, I am able to do TTS. The volume setting in the "Speak" command seems to be ignored though. The text and voice selection work, but not the volume.

This beta integration has always seemed to be a bit hit or miss, so I use Node Red to do any TTS. The nodered-contrib-cast-v2 nodes create a persistent (if that's the right word) connection to each Google speaker so I can monitor the connections and send a notification if one of the connections drops.

image

1 Like
9

I don’t use the delay. Never have. It always worked ok before.

10

Same here.

11

Same here

12

Same problem here. Rolled back to .130 and it works.

1 Like
13

Same here. Rolled back to .130 and it works

1 Like
14

Tagging @gopher.ny

16

Other than Chrome Cast, what else is “broken”?

3 Likes
17

Anything that requires access to java.util library.

18

Such as????

2 Likes
19

The dashboard (some components), any timers, rule machine if using specific function calls, anything that uses the java libraries that are built-in. It could be anything depending on the developer. I posted the fix on GitHub if people want to manually tweak. Otherwise I'd recommend rolling back until they fix it in the next version.

20

All my speakers are working. But, I have an initialization rule running every few hours.

21

I’m using java libraries in a lot of places and haven’t seen an issue. If this was a big issue I’m sure there would be a lot more issues being reported. As you stated earlier you can roll back to .130 if it is an issue for you.

1 Like
22

You'll have an issue once the device or whatever it's doing requires a refresh command to work properly.