Home Assistant pulls hourly spot prices through the Tibber integration or the Nordpool HACS add-on. It then schedules EV chargers, water heaters, heat pumps, and dishwashers during the cheapest hours. On a 2026 Nordic tariff with 3-8x daily price swings, shifting 10-15 kWh of flexible load each day cuts the bill by 20-40% with no comfort cost.

Why Dynamic Pricing Pays Off in 2026

The Nordpool day-ahead auction closes around noon CET. By 13:00, prices for all 24 hours of the next day are out for every bidding zone. That window is exactly what Home Assistant needs: a once-a-day drop of 24 hourly prices that your automations can plan against overnight.

AppDaemon 4.5.14 is a Python runtime that runs next to Home Assistant . It lets you write rules as full Python classes. You get state machines, scheduling, outside API calls, and logic that YAML can’t handle. Install it as a Home Assistant add-on, drop a Python file in the apps folder, define a class that inherits from hass.Hass, and use callbacks like listen_state() and run_daily() to drive multi-step flows, saved values, and live data.

Home Assistant Blueprints are reusable automation templates. They split the logic from the per-device bits. You define a pattern once, say a motion light with a timeout, then spin it up for every room by filling in a form. No YAML to copy. No ten near-twin automations to babysit. In Home Assistant 2026.4, blueprints span three domains: automation, script, and template. They ship dozens of selector types for clean input forms and tidy collapsible sections for bigger setups. They’re the fastest way to keep smart home behavior the same across many devices.

Yes, Home Assistant ships a built-in conditional card. It shows or hides any dashboard card based on live state: entity value, time of day, who is home, screen size, and more. Add template sensors and a few HACS cards, and you can build dashboards where morning shows weather and coffee buttons, evening shows media and light scenes, and an empty house shows cameras and alarm controls. Cards pop in and out without leaving blank gaps, all through the stock Lovelace frontend. No custom code needed.

Use Home Assistant ’s built-in packages system. Instead of one giant configuration.yaml that grows into a 2,000-line beast, packages let you split YAML by function: packages/lighting.yaml, packages/climate.yaml, packages/security.yaml, and so on. Each file can hold any mix of automations, sensors, scripts, input helpers, and templates. To tweak your thermostat logic, you open packages/climate.yaml. Nothing else.

As of Home Assistant 2026.4, packages support every integration domain, !secret references, Jinja2 templates, and nested subfolders. The rest of this post walks through setup, migration, design patterns, and Git workflows that make packages practical for a real smart home.

Gatus is a single-binary monitoring tool that probes your services and shows a public status page at a URL you control. You define every check in one YAML file. So your whole setup can live in Git next to the rest of your stack. There is no need for a database, no web UI to click through, and no per-monitor pricing. If you self-host a blog, a Gitea instance , a Home Assistant server, or a mail relay, Gatus gives you a simple way to know when something breaks.