Closed stang70man closed 7 months ago
If this is the same bug, it sounds like it's working better for you than most of us 🙃
If this is the same bug, it sounds like it's working better for you than most of us 🙃
I had this issue early on when I was running Proxmox on an old Intel Dual Core processor with limited memory. I replaced my hardware with an Intel i5 Gen6 processor 6 or 8 cores and with 32Gb of memory and threw more memory at the VM and that helped it a bunch. This was an upgrade I needed to do anyway, but performance on wake word pushed me to go ahead. Not saying that will work for anyone else, but it certainly solved my earlier issues.
I found a recommendation to change my wake word to something else, so I did and I had no further issues. I decided to change it back to my original wake word "OK Jarvis" and it's been working for several days with no additional issues. Something else along the way may have resolved the issue. Closing this as it seems to be resolved.
Describe the issue you are experiencing
I am finding an error with the openwakeword addon after some indeterminate time. (Usually within 24 hours or so.) Restarting the openwakeword service will bring the voice assistants back online until I receive the error again.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
CEC Scanner
What is the version of the add-on?
Openwakeword v1.8.2
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1404 Downloaded Repositories | 44 HACS Data | okHome Assistant Cloud
logged_in | true -- | -- subscription_expiration | January 31, 2025 at 6:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | true remote_server | us-east-1-1.ui.nabu.casa certificate_status | ready instance_id | 18ace9f2c705453a8c19e89cdc4deaec can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okEyeOnWater
api_endpoint_reachable | ok -- | --Home Assistant Supervisor
host_os | Home Assistant OS 11.5 -- | -- update_channel | stable supervisor_version | supervisor-2024.02.0 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 156.8 GB disk_used | 36.1 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Samba share (12.3.0), Terminal & SSH (9.9.0), UniFi Network Application (3.0.3), File editor (5.8.0), Home Assistant Google Drive Backup (0.112.1), Network UPS Tools (0.13.0), Zigbee2MQTT (1.35.3-1), RTSPtoWeb - WebRTC (1.4.0), Tailscale (0.16.0), Whisper (1.0.2), Piper (1.4.0), openWakeWord (1.8.2), ESPHome (2024.2.0), Studio Code Server (5.15.0)Dashboards
dashboards | 3 -- | -- resources | 30 views | 36 mode | storageRecorder
oldest_recorder_run | February 21, 2024 at 3:03 AM -- | -- current_recorder_run | February 21, 2024 at 8:21 PM estimated_db_size | 811.78 MiB database_engine | sqlite database_version | 3.44.2Spotify
api_endpoint_reachable | ok -- | --Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
No response