Control plane
Home Assistant is the hub for lighting, climate, locks, sensors, and presence across both properties, with automations versioned as code.
I'm Eugene Brink — a technical program manager working across data center infrastructure, supply chain, and hardware platforms. This is where I write about that work and run the automation stack for my two homes.
Home automation
Everything runs on hardware I own, in containers I can rebuild from a private Git repository. No vendor lock-in, no cloud dependency for anything that has to keep working when the internet doesn't.
Home Assistant is the hub for lighting, climate, locks, sensors, and presence across both properties, with automations versioned as code.
Two Ubuntu servers split the load — one runs automation and monitoring, the other serves this site. Portainer gives both a single pane of glass.
Prometheus scrapes node and container exporters on both hosts; Grafana turns that into dashboards for uptime, energy use, and storage headroom.
Admin surfaces stay private on a Tailscale mesh. Only the public site reaches the internet, proxied and TLS-terminated at Cloudflare.
My places
Each home has its own page — the hardware in it, what's automated, and what the weather is doing outside.
A hilltop lot above Long Beach with harbor views, hard sun, and a cooling problem worth solving with software.
Visit Signal Hill 47.6062° N · 122.3321° WThe Pacific Northwest house — rain sensors, humidity management, and lighting that compensates for four months of grey.
Visit SeattleAbout
My background is asset tracking and inventory systems, RFID and hardware management, data center migrations, and platform delivery across web, iOS, and Android. Most of that work has one thing in common: many teams, one immovable date, and a physical constraint you can't refactor away.
Off the clock, the same instincts show up in the home lab — version control, monitoring, documented rollback, and a strong preference for owning the infrastructure rather than renting it.