Google Home Exposure Manager - UI for managing which entities are exposed to Google Home

Share your Projects!
,
1

Hi everyone,

I built a custom integration that adds a UI for managing which entities are exposed to the manual Google Assistant integration. Instead of hand-editing YAML to control entity_config, you get a sidebar panel where you can toggle exposure, set up bulk rules, and preview changes before saving.

What it does:

  • Bulk rules ā€“ expose entire domains, exclude areas, or use wildcard patterns (e.g., *_battery to hide all battery sensors)

  • Individual overrides ā€“ always-expose or never-expose specific entities, overriding bulk rules

  • Device rules ā€“ control exposure for all entities from a device at once

  • Aliases & custom names ā€“ set voice-friendly names for Google Home

  • Preview before save ā€“ see exactly what will change before writing to disk

  • Automatic migration ā€“ imports your existing entity_config on first setup, preserving names, aliases, and room hints

  • Safety ā€“ automatic timestamped backups, atomic writes, non-destructive uninstall

DeviceAndEntities
DeviceAndEntities1221Ɨ901 63.4 KB

BulkRules
BulkRules1223Ɨ713 51.6 KB

PreviewAndSave
PreviewAndSave656Ɨ759 39.1 KB

Requirements:

Install via HACS:

  1. HACS ā†’ Three dots ā†’ Custom repositories

  2. Add: https://github.com/NathanMagnus/GoogleHomeExposureManager

  3. Category: Integration

  4. Install and restart

GitHub: GitHub - NathanMagnus/GoogleHomeExposureManager: A Home Assistant HACS integration for managing Google Assistant entity exposure with a visual UI.

Full disclosure: this was vibe coded with AI assistance, but it has full test coverage, automatic backups before any file changes, and atomic writes to prevent corruption. Feedback, bug reports, and contributions welcome. This is v0.1.0 ā€“ Iā€™d especially appreciate hearing from anyone who tries it on their setup.

3 Likes