heinemannj /
home-assistant-config
Home Assistant Configuration & Documentation for my Smart House. Write-ups, part lists, and links throughout.
55/100 healthLoading repository data…
frenck / repository
:house: My Home Assistant configuration, a bit different that others :) Be sure to :star2: this repository for updates!
A transparent discovery signal based on current public GitHub metadata.
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
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.
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 directory. No giant here :sweat_smile:
Selected from shared topics, language and repository description—not editorial ratings.
heinemannj /
Home Assistant Configuration & Documentation for my Smart House. Write-ups, part lists, and links throughout.
55/100 healthincludes08 /
:house_with_garden: Open source home automation that puts local control and privacy first
28/100 healthavidit /
:house_with_garden: my home automation config
44/100 healthintegrations/configuration.yamlFeel free to poke around, steal ideas, or get inspired. Be sure to hit the :star2: if you find it useful!
integrations/, loaded as
packages.
Clean, organized, easy to find stuff.stable, beta, and dev versions of Home Assistant Core. If something
is going to break, I'll know before it hits a release :muscle:.
├── 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.
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:
Want to learn more or get involved? Here are some good starting points:
The original setup of this repository is by Franck Nijhof.
For a full list of all authors and contributors, check the contributor's page.
MIT License
Copyright (c) 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.