home-assistant-config

Frenck’s Home Assistant Configuration

What is Home Assistant?

Not familiar with Home Assistant? Oh, you’re in for a treat! :wink: It’s an open source smart home platform that runs locally on, for example, a Raspberry Pi. It connects to over 2,000 different devices and services, from lights and sensors to media players and EVs, all without relying on some cloud. It’s one of the most active open source projects on GitHub and is backed by the Open Home Foundation.

About

Hey! :wave: This is my personal Home Assistant configuration. I’m Frenck, the lead of the Home Assistant project and Chair of the Leader Committee at the Open Home Foundation.

I like to keep things tidy, so the whole configuration is modular using Home Assistant’s packages pattern. Every integration gets its own file in the integrations/ directory. No giant configuration.yaml here :sweat_smile:

Feel free to poke around, steal ideas, or get inspired. Be sure to hit the :star2: if you find it useful!

Key Features

• Fully modular. Each integration lives in its own YAML file under integrations/, loaded as packages. Clean, organized, easy to find stuff.
• Tested every night. This config is validated daily against the stable, beta, and dev versions of Home Assistant Core. If something is going to break, I’ll know before it hits a release :muscle:
• ESPHome ready. Got a dedicated directory and CI workflow for ESPHome device configurations.
• Linted to the bone. yamllint, remarklint, Prettier, actionlint, and zizmor all run on every commit. Yes, I take my YAML seriously.
• Automations, scripts & scenes. All split into their own directories, making it easy to manage as things grow.

Repository Structure

.
├── configuration.yaml        # Minimal bootstrap, loads packages
├── integrations/             # Modular integration configs (packages)
├── automations/              # Split automation YAML files
├── scripts/                  # Split script YAML files
├── scenes/                   # Split scene YAML files
├── blueprints/               # Automation & script blueprints
├── esphome/                  # ESPHome device configurations
├── secrets.yaml              # Secrets (not in repo)
└── secrets.fake.yaml         # Fake secrets for CI testing

The configuration.yaml is intentionally minimal. It only loads the integrations/ directory as packages. Each integration gets its own file, keeping things clean and easy to navigate.

Contributing

I consider my personal Home Assistant configuration an active open-source project. So if you feel like adding an improvement, feel free to contribute.

We have set up a separate document containing our contribution guidelines.

Thank you for being involved! :heart_eyes:

Useful Links

Want to learn more or get involved? Here are some good starting points:

• Home Assistant Website
• Home Assistant Documentation
• Home Assistant Community Forums
• Home Assistant Discord
• ESPHome Website
• Open Home Foundation

Authors & contributors

The original setup of this repository is by Franck Nijhof.

For a full list of all authors and contributors, check the contributor’s page.

License

MIT License

Copyright © 2018-2026 Franck Nijhof

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.