// the take
This is Frenck's (Home Assistant core maintainer and Open Home Foundation chair) personal Home Assistant configuration, published as a reference for how to structure a non-trivial HA setup using the packages pattern. It's aimed at HA users who want a real-world example of modular config organization rather than a monolithic configuration.yaml, not at anyone looking for a reusable tool.
Genuinely clean use of HA's packages pattern - every integration gets its own YAML file under integrations/, which is the right way to keep a growing HA config navigable. CI validates the config nightly against HA stable, beta, and dev builds, so breaking changes in HA itself get caught before they land. The lint stack (yamllint, remarklint, Prettier, actionlint, zizmor) is unusually thorough for a personal dotfiles-style repo and models good CI hygiene for YAML-heavy projects. ESPHome configs get their own directory and workflow instead of being bolted onto the main config as an afterthought.
The automations/, scripts/, scenes/, and blueprints/ directories only contain .gitkeep in the tree - the actual substance of a home automation setup is either stripped out or lives elsewhere, so there's less to actually learn from than the README implies. It's one person's config tied to his specific devices and home layout, not a template or library, so there's nothing to install and no compatibility guarantee - things get added or removed as his house changes, with no versioning for anyone copying snippets. Secrets are excluded and swapped for secrets.fake.yaml in CI, which is correct practice but means you can't run this as-is; you're reverse-engineering your own values against an incomplete example.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →