Closed kizovinh closed 7 months ago
Hi,
I will have a look at this. Is there a specific way to reproduce this?
Also have you checked your API keys and region?
Hi,
I will have a look at this. Is there a specific way to reproduce this?
Also have you checked your API keys and region?
The api keys are region are remain the same, they are matched. I am not sure how to reproduce this issue, I am using vietnamese for the pipeline and they just stop working. Everytime I speak to the voice assistant it throw these error above in the add on logs
So it did work before?
So it did work before?
Yes it work fine till end of Jan, I just notice that it stop working since last week
I have updated some packages. Please try with the new version. Unfortunately I can't test it now as I am not home.
Hi can you try version 1.0.6? I hope this will solve things.
Hi can you try version 1.0.6? I hope this will solve things.
I updated, but the error remain the same
DEBUG:wyoming_microsoft_stt.handler:Sent info
DEBUG:wyoming_microsoft_stt.handler:Sent info
DEBUG:wyoming_microsoft_stt.handler:Language set to vi-VN
DEBUG:wyoming_microsoft_stt.handler:Receiving audio
DEBUG:wyoming_microsoft_stt.handler:Audio stopped
WARNING:wyoming_microsoft_stt.microsoft_stt:Speech Recognition canceled: CancellationReason.Error
WARNING:wyoming_microsoft_stt.microsoft_stt:Error details: Connection failed (no connection to the remote host). Internal error: 1. Error details: Failed with error: WS_OPEN_ERROR_UNDERLYING_IO_OPEN_FAILED
wss://southeastasia.stt.speech.microsoft.com/speech/universal/v2
X-ConnectionId: bec0d1f29b7d4b699370c19d3bb7038a SessionId: bec0d1f29b7d4b699370c19d3bb7038a
INFO:wyoming_microsoft_stt.handler:None
DEBUG:wyoming_microsoft_stt.handler:Completed request
DEBUG:wyoming_microsoft_stt.handler:Sent info
DEBUG:wyoming_microsoft_stt.handler:Sent info
Hi can you try version 1.0.6? I hope this will solve things.
Could you please enable the sdk log, or something thst give more information. I still face the issue with all the language.
Hi Hugo, I got this issues recently since this month, maybe after update. Could you please take a look. Here are the logs: