-
-
Notifications
You must be signed in to change notification settings - Fork 33.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Cloud STT throws 503 error on first run #139290
Comments
Hey there @lufton, @tronikos, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) google_cloud documentation |
Which STT model and language are you using? |
Language: sv-SE |
Also happens to me from time to time:
Trying again after failure then works correctly. |
The problem
I've not tested this very thoroughly yet, but from googling I would guess that it, after the first fail, works for about 120 seconds whereupon it fails after that. This leads to me having to wake my assistant twice every time when using google_cloud as stt provider.
Log:
2025-02-25 20:29:03.176 ERROR (MainThread) [homeassistant.components.google_cloud.stt] Error occurred during Google Cloud STT call: 503 recvmsg:Connection reset by peer
2025-02-25 20:29:03.298 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [135241260007776] Received binary message for non-existing handler 1
What version of Home Assistant Core has the issue?
System Information version | core-2025.2.4 -- | -- installation_type | Home Assistant Container dev | false hassio | false docker | true user | root virtualenv | false python_version | 3.13.1 os_name | Linux os_version | 6.8.0-52-generic arch | x86_64 timezone | Europe/Stockholm config_dir | /config
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 5000 Installed Version | 2.0.5 Stage | running Available Repositories | 1615 Downloaded Repositories | 8Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okDashboards
dashboards | 6 -- | -- resources | 3 views | 5 mode | storageNetwork Configuration
adapters | lo (disabled), eth0 (enabled, default, auto) -- | -- ipv4_addresses | lo (127.0.0.1/8), eth0 (172.18.0.4/16) ipv6_addresses | lo (::1/128), eth0 () announce_addresses | 172.18.0.4Recorder
oldest_recorder_run | February 14, 2025 at 08:35 -- | -- current_recorder_run | February 24, 2025 at 16:54 estimated_db_size | 59.59 MiB database_engine | sqlite database_version | 3.47.1What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Google Cloud
Link to integration documentation on our website
https://www.home-assistant.io/integrations/google_cloud
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: