Very excited to found out the Chromecast Integration, but seems all my TTS trials were cut to ~2 seconds. I have tried to send TTS in the device page to my Google Home Max and Nest Hub. Both of them made the cast sound and start to speak, but both of their audio get cutoff (the cast just stopped) after ~2 seconds.
Sample log attached below:
status idle Kitchen Display is idle DEVICE 2022-06-29 11:21:30.928 PM PDT
mediaSource None Kitchen Display media source is None DEVICE 2022-06-29 11:21:30.925 PM PDT
status playing Kitchen Display is playing DEVICE 2022-06-29 11:21:29.365 PM PDT
status buffering Kitchen Display is buffering DEVICE 2022-06-29 11:21:28.826 PM PDT
mediaSource Hubitat Kitchen Display media source is Hubitat DEVICE 2022-06-29 11:21:27.444 PM PDT
Is the beginning of the audio getting cutoff or the back end? I had the beginning portion get cut off and I put an ! in front of the text and that fixed it.
interesting... mine isnt speaking at all now. this just started in the last few days. it used to make the noise and then announce which door was open. now i can even get it to speak if i init the device and then try to manually use the speak button. anyone else notice this?
so i was trying to get it to say test and that didnt work... but putting in "1 2 3 4" and pressing speak it makes a quick noise like it is trying to say 1. can someone please look into this app and fix it so the speech works again? not sure who maintains it since it is built in. but this def worked before a recent update to the hub.
ok... looks like if you change the delay before speaking to something besides "none" (i changed mine to 1 sec) then the speech works again. so I would say this is def a bug with the "none" or no delay before speaking setting. this wasnt a problem before so not sure when this started but can someone on the hubitat team look into it?
Quick update. The audio starts to work fine today, I absolutely did nothing, but today the audio can be played without been cutting off. Will report back jd reproduced.