neopholus
commented
6 months ago I analyzed the problem and found a way to fix it:
On the iobroker server, open /opt/iobroker/node_modules/iobroker.sayit/lib/speech2device.js in e.g. nano, search for TIMEOUT and in the surrounding if-block
change if (count > 20) {
to if (count > (duration+1)*2) {.
Result:
if (count > (duration+1)*2) {
clearInterval(intervalHandler);
intervalHandler = null;
this.adapter.log.error(`Error while checking if ${chromecastAnnouncementDev} finished playing announcement: ${announcementJSON}: TIMEOUT`);
reject('Timeout by checking of announcement finished playing');
return;
}Save changes and do not forget to restart all sayIt instances in iobroker.
Then the error messages are gone. All the hard work of figuring out the length of the spoken text was already done, it was just not used. Maybe somebody can change this in the github version.
Apollon77
crunchip77
Describe the bug
When playing a longer announcement (e.g. weather forecast) using sayit on a Google Home Mini via chromecast, there are two lines of errors in the log from the sayit adapter (not from chromecast):
Error while checking if chromecast.0.Google_Home_WZ.player.announcement finished playing announcement: {"url":"http://192.168.X.YYY:ZZZZ/sayit.0/tts.mp3?ts=1705256129645","volume":20}: TIMEOUTCannot play file: Timeout by checking of announcement finished playing.The announcement is spoken correctly nevertheless.
To Reproduce
Steps to reproduce the behavior:
20;<speak>Das ist eine lange Testansage, um einen Fehler im Log zu provozieren. Und da das noch nicht lange genug ist, fügen wir noch weiteren Text hinzu. Sicherheitshalber noch einen dritten sehr langen Satz, damit das Problem auch wirklich auftritt. Ich hoffe, das hat gereicht.</speak>Expected behavior
Announcement should be spoken WITHOUT an error message in the log.
Screenshots & Logfiles
Error while checking if chromecast.0.Google_Home_WZ.player.announcement finished playing announcement: {"url":"http://192.168.3.105:8083/sayit.0/tts.mp3?ts=1705256699645","volume":20}: TIMEOUTCannot play file: Timeout by checking of announcement finished playing.Versions:
Additional context
I think, sayit is using the datapoint
announcementto playback via chromecast and then waiting for the end of the playback. As the playback lasts quite long, the timeout gets active and thinks, there is a problem, but in reality the file is still playing. Maybe, setting the timeout depending on the length of the mp3 file (e.g. using mp3info) would be a solution? Or making the timeout configurable?