// the find
CCOSTAN/Home-AssistantConfig
:house: Home Assistant configuration & Documentation for my Smart House. Write-ups, videos, part lists, and links throughout. Be sure to :star: it. Updated FREQUENTLY!
A personal Home Assistant configuration for one house, published for reading rather than installing. The useful part is how it is organized: feature packages, dashboards split by view, and two custom components for Cloudflare alerts and Tesla charge guarding. It is aimed at Home Assistant users who already run a similar setup and want to see how someone else wired up alerts, Docker telemetry, and vacuum logic.
The cloudflare_alerts component is the strongest piece: authenticated webhooks, persistent Repairs entries, and a separate policy.py, which suggests the decision logic is kept apart from the integration glue. The config is split into roughly fifty packages, one per device or concern, so the vacuum, Powerwall, or sprinkler logic can be read on its own without wading through one large configuration.yaml. The issues double as a design log, which the README states outright, and that trail explains why things changed in a way the YAML never does. The repo has CI workflows for config validation and secret scanning, which is more than most personal config repos bother with.
The README says this is not a clone-and-run setup, and it isn't. Entity IDs, Docker host names like docker_10 and docker_14, and fixed LAN addresses such as 192.168.10.10 run through most files, so lifting a package means rewriting most of it. Dashboards are duplicated across the overview, infrastructure, bedroom, kiosk, and kiosk_satellite_staging trees with overlapping partials, and nothing in the repo says which one is current. The language tag says Python, but the bulk is YAML, Jinja, and shell; the Python is mostly the two custom components, and no test directory shows in the truncated tree. The rationale for many features lives in linked blog posts and YouTube videos rather than the repo, so those explanations are only as durable as the links, and the affiliate gear table makes parts of the README read like a store page.