github-actions[bot]
commented
7 months ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the issue you are experiencing
After HA restarts/reboots, the Google Assistant SDK add-on will not run. It starts and then fails with the error listed below. I just upgraded to core 2024.2.5. I restored back to 20.24.1.6, but have the same problem. SDK was working without issues last week.
Errors in log: s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. [16:40:39] INFO: Installing/Updating service client_secrets file [16:40:39] INFO: Starting WebUI for handling OAuth2... Traceback (most recent call last): File "/usr/bin/hassio_oauth.py", line 119, in
user_data = json.load(data)['installed']
KeyError: 'installed'
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
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?
2.5.0
Steps to reproduce the issue
1.Reboot or restart Home Assistant. SDK fails to start. If I manually start it, I can see it starting in the log, but fails moments later with the error listed in the description.
System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4793 Installed Version | 1.34.0 Stage | running Available Repositories | 1473 Downloaded Repositories | 37Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | June 30, 2024 at 8: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-7.ui.nabu.casa certificate_status | ready instance_id | c6246d9e8801469bbd8c19c461351fa9 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.0 -- | -- update_channel | stable supervisor_version | supervisor-2024.02.0 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 219.4 GB disk_used | 15.5 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (17.1.1), Studio Code Server (5.15.0), Samba share (12.3.0), HA Scheduler (0.17), Home Assistant Google Drive Backup (0.112.1), Piper (1.5.0), Whisper (1.0.2), Mosquitto broker (6.4.0), openWakeWord (1.10.0), Music Assistant BETA (2.0.0b106), Google Assistant SDK (2.5.0)Dashboards
dashboards | 3 -- | -- resources | 17 views | 55 mode | storageRecorder
oldest_recorder_run | February 18, 2024 at 5:13 PM -- | -- current_recorder_run | February 28, 2024 at 4:34 PM estimated_db_size | 341.81 MiB database_engine | sqlite database_version | 3.44.2Xiaomi Miot Auto
component_version | 0.7.15 -- | -- can_reach_server | ok can_reach_spec | ok logged_accounts | 1 total_devices | 1Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
SDK was working on 2024.1.6. I upgraded to 2024.2.4 on Feb 26 and then to 2024.2.5 on Feb 28. Both February releases have the problem with SDK. I restored back to 2024.1.6, but SDK still fails to start.