The household automation estate

Automation & AI

The household automation estate

Eleven n8n workflows that run my life admin.

Problem

Shift work, dynamic energy pricing, a home server fleet, and a roster that changes without warning. Nothing was on fire, but a dozen small things needed watching: shift changes inside the week, payslip errors, cheap power windows, server health, backups. Checking them manually is exactly the kind of low-value, high-frequency work that should not be a human's job.

Diagnosis

Most of the friction was data movement. A roster lives in a calendar feed, payslips arrive by email, energy prices come from an API, server health comes from SSH. Nothing needed building from scratch; it needed connecting. An automation runner plus a set of small, single-purpose workflows would cover it.

Action

  • Shift-change watchdog — diffs the rostering calendar hourly and alerts on changes inside the next seven days
  • Roster pipeline — rebuilds the roster every 15 minutes and publishes the next shift to Home Assistant as a sensor
  • Payslip check — Gmail-triggered; parses the payslip PDF and compares it against actual shift history
  • Morning digest — 07:00, one message with energy prices, the cheap window, weather and infrastructure status
  • Cheap-power alert — checks live energy pricing every 15 minutes
  • Infrastructure watchdog — SSH health checks across the fleet every 15 minutes, alerts on failures
  • Mesh visualiser — a live map of the mesh (webhook)
  • AI assistant — a chat agent over Gmail, Home Assistant and memory (webhook)
  • Nightly export — 02:30, exports all workflows and encrypted credentials, keeps 14 versions
  • Price-aware heating and water heater — event-driven from live energy pricing
  • Budget rules — categorisation and payee tooling over exported transactions

Outcome

  • Shift changes no longer surprise me; the watchdog tells me within the hour
  • Payslips are verified against shifts automatically instead of by eye
  • Household energy use follows the cheap windows without me thinking about it
  • Fleet problems page me before I notice them
  • Eleven workflows, one runner, all versioned and exported

What I'd do differently

Pending

Reflection to be written by Jupiter.

Clock
--:--:--—Local time