Smart home automation, run like a production system
A self-hosted smart home built on Home Assistant. It ties Z-Wave and Wi-Fi devices together with scheduled automations, room-by-room control, alerts, voice control and energy monitoring. The whole configuration lives in git and reaches the house through an automated pipeline, with the same discipline we apply to client systems.
- Status
- In daily use; in version control since April 2026
- Platform
- Home Assistant on our own Proxmox server
- Scale
- About 1,950 entities: devices, sensors and helpers
- Source
- Private — walkthrough on request
What it does
Z-Wave and Wi-Fi in one system
Z-Wave dimmers and switches work alongside Wi-Fi heating and climate devices. Every entity follows one naming scheme by type, floor and room, so automations, groups and dashboards stay readable as the house grows.
Alerts that reach a person
More than 30 alert conditions cover security, batteries, climate, weather, maintenance and system health. Severity decides who is notified and how, critical alerts repeat every five minutes until someone acknowledges them, and acknowledgements clear themselves once the problem is gone.
Presence from several signals
Home or away is decided from the Wi-Fi network, the router and GPS, each with a limit on how old the data may be, so a stale location does not trigger the wrong automation.
Voice control in Norwegian
Custom Norwegian commands answer questions about the house, such as indoor temperature, today's energy use and the weather. A voice assistant backed by a language model runs the home's scripts and can call our own services.
Energy and weather
Consumption from the metered devices is rolled into one total for the long-term energy dashboard, and forecast data from MET Norway feeds the weather sensors and the wind and temperature alerts.
Servers report in the same place
The uptime monitor for our servers and the off-site backup job report into the same alert system, so a service that goes down or a backup that fails shows up on the phone like any other alert.
Relevant if you're looking for…
This is our own house, in daily use, and we are happy to walk you through how it is set up.
- A smart home system with Z-Wave and Wi-Fi in one place: dimmers, switches, heating and climate are controlled room by room, and all of the roughly 1,950 entities follow one naming scheme by type, floor and room.
- Home Assistant automation ideas from a house in daily use: home or away comes from Wi-Fi, the router and GPS with a limit on how old each signal may be, and more than 30 alert conditions cover security, batteries, climate and weather.
- A self-hosted server for the house on Proxmox: the home system runs as a virtual machine next to containers for monitoring, uptime checks and backups, with three backup tiers, one of them off-site.
- Voice control in Norwegian: custom commands answer questions about indoor temperature, today's energy use and the weather, and a voice assistant backed by a language model runs the home's scripts.
We build this for clients: Industrial and secure control-system software · Custom software and internal tools
How it works
- 01
Change
Configuration is edited in git and reviewed like code.
- 02
Push
A push to the main branch starts the deploy.
- 03
Deploy
CI copies only managed files; secrets and runtime state are left alone.
- 04
Apply
A reload or a restart, chosen by which files changed.
How it's built
Home Assistant runs as a virtual machine on our own Proxmox server, next to containers for monitoring, uptime checks and backups. The configuration is split by topic: automations in numbered files, one package per feature, and template sensors with safe default values, so a device that drops offline raises no false alarm.
Deploys are GitOps. A push to main starts GitHub Actions, which joins our private network, updates a staging copy on the box and copies over only the managed paths. Secrets live in a file that is never committed, and backups run in three tiers: frequent local snapshots, nightly backups of the virtual machines and containers, and a daily off-site copy.
Engineering highlights
- All configuration in git, deployed by CI over a private network
- Secrets never committed; a deploy never touches runtime state
- Reload or restart picked automatically from what changed
- Guarded sensor templates: an offline device raises no false alarm
- Three backup tiers, one of them off-site, with a written restore playbook
Questions
Can the configuration live in git and deploy like code?
Yes. Here the whole configuration lives in git, and a push to main starts GitHub Actions, which copies over only the managed files and picks a reload or a restart based on what changed. Secrets are never committed.
How do you stop false alarms when a device drops offline?
Template sensors have safe default values, so a device that drops offline raises no false alarm. Critical alerts repeat every five minutes until someone acknowledges them, and the acknowledgement clears itself once the problem is gone.
Can Agentas help with a setup like this?
This is our own house, and we are happy to walk you through how it is built. For businesses, we build the same kind of automation, alerting and monitoring.
Want something like this?
We run a home the way we run client systems: configuration in version control, automated deploys, alerts that reach a person, and backups with a tested way back.
Get in touch