Repository navigation
feat!: v3.0.0 .storage-native zero-reboot Google Assistant architecture - #5
Merged
Merged
Conversation
added 8 commits
October 17, 2026 15:18
…o-reboot architecture
…o Google and credentials UI
…lifecycle handler for clean uninstall
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upgrades Google Assistant Entity Console to v3.0.0 (major release), replacing the YAML generation + Home Assistant reboot workflow with a 100%
.storage-native, zero-reboot live sync architecture.Key Changes
.storagePersistence (store.py):google_settings(project_id,service_account(client_email,private_key),report_state,secure_devices_pin,auto_sync),synced_entities,blocklist, andai_settingsinside.storage/google_assistant_entity_consoleviahomeassistant.helpers.storage.Store.configuration.yaml,secrets.yaml,gaGen_*.yaml,SERVICE_ACCOUNT.json,.google_assistant_blocklist.json, and.google_assistant_ai_settings.jsonon first run.runtime.py):google_assistantconfig entry (yaml_attachedmode) or bootstrapsGoogleConfig+GoogleAssistantView(/api/google_assistant) directly from.storage(storagemode) without requiringgoogle_assistant:inconfiguration.yaml.google_config._config["entity_config"]in memory on every entity exposure, nickname, or friendly-name update.await google_config.async_sync_entities_all()(devices:requestSyncto Google HomeGraph) on Sync to Google (or via optional 15s debouncedasync_schedule_google_sync_all()) with zero Home Assistant restarts.SOURCE_IMPORTgoogle_assistantconfig entries when switching to standalone.storagemode so Home Assistant boots cleanly aftergoogle_assistant:is removed fromconfiguration.yaml.views.py,static/index.html,static/app.js):/api/google_assistant_entity_console/sync,/api/google_assistant_entity_console/google_settings, and/api/google_assistant_entity_console/migrate_yaml..storage) credentials & Migrate from YAML controls to the Settings modal.Visual Screenshots
v3.0.0
.storageLive Sync Dashboardv3.0.0
.storageGoogle Assistant & AI Settings ModalVerification
359 passed(test_store.py,test_runtime.py,test_views.py,test_blocklist.py,test_entities.py,test_yaml.py,test_config_flow.py,test_playwright_e2e.py).ruff check .passed with 0 errors.store.py,runtime.py, andviews.pyagainst the runninghomeassistantcontainer (GoogleConfig,GoogleAssistantView,Store, and live/configYAML/secrets/service-account extraction).