5 Home Assistant Automations for a Smarter, Cozier Home

Living in Norway means embracing dramatic seasons: endless summer daylight and deep, dark winters. coupled with some high electricity prices. This unique environment makes a local, powerful, and flexible smart home platform like Home Assistant (HA) essential. It serves as a practical tool for comfort, security, and cost savings.

But a powerful system is only as good as the automations you build. Forget generic “turn on the light” routines. Let’s dive into five high-impact and practical automations. These are tailored for a Norwegian household. We will use integrations and projects you likely already have or are planning to add.

---

1. Intelligent Security Presence Simulation with Eufy Security

The Problem: Traditional “away mode” automations that just toggle lights randomly are obvious. A sophisticated burglar will notice patterns. You need a simulation of genuine human activity. 

The Solution: Use your Eufy Security cameras and sensors. They run via the local Eufy Security integration. These devices can trigger a response based on actual detected motion. This creates a believable “someone’s home” effect only when it’s needed.

How it Works:

1. HA monitors your Eufy door/window sensors and camera motion zones.
2. When the system is “armed” (based on your presence), any sensor trigger (e.g., a cat in the garden, a neighbor at the door) initiates a sequence.
3. This sequence activates lights in logical and connected rooms (not just random bulbs). It mimics movement paths. It also plays short audio clips from a speaker.

Why it’s Perfect in Norway: During the long, dark winter months, this automation runs more frequently. It provides crucial peace of mind when you’re at your cabin or away for the weekend. It uses your existing security hardware intelligently.

Example (YAML – Simplified Presence Simulator):

automation:
  - alias: "Eufy Security - Presence Simulation Trigger"
    trigger:
      platform: state
      entity_id: binary_sensor.eufy_entryway_motion
      to: "on"
    condition:
      # Only run if we are marked as 'not_home'
      condition: state
      entity_id: person.your_name
      state: "not_home"
      # And only between sunset and sunrise (when lights are visible)
      condition: sun
      after: sunset
      before: sunrise
    action:
      service: light.turn_on
      target:
        area_id: living_room  # Activates a group of lights
      data:
        brightness_pct: 75
        transition: 3
    mode: restart  # Prevents multiple overlapping sequences

Pro Tip: Use a Node-RED flow for more complex paths. Trigger on the Eufy sensor, use a function node to randomly select from a list of pre-defined “activity patterns” (e.g., “kitchen to hallway,” “home office on”), then execute the sequence with call service nodes.

---

2. Z-Wave Multi-Sensor Thermal Comfort & Frost Protection

The Problem: A thermostat in one room doesn’t represent your whole home’s temperature. A cold basement or a hot attic can lead to wasted energy, frozen pipes, or discomfort. 

The Solution: Deploy multiple Z-Wave temperature/humidity/motion sensors (like the Aeotec Multisensor 6) in key zones. Create a “Thermal Comfort” virtual sensor. It averages temperatures from living areas. It uses the coldest sensor reading from “risk zones” (basement, crawl space) for critical actions.

How it Works:

1. Sensors report °C every 5-10 minutes.
2. An template sensor calculates the average temperature of your main living zones.
3. A separate template sensor finds the minimum temperature from your basement and exterior wall-adjacent rooms.
4. Automations use these values:
   • If average comfort temp < 19°C, gently notify you.
   • If risk zone temp < 5°C, send a critical alert and turn on a dedicated frost-protection heater.

Why it’s Perfect in Norway: Prevents costly pipe bursts in detached parts of the house during a -15°C snap. It also helps you balance heating—maybe your bedroom is at 18°C while the living room is 22°C. You can adjust the system based on real data, saving kWh.

Example (Template Sensors & Automation YAML):

template:
  - sensor:
      - name: "Living Area Average Temperature"
        unit_of_measurement: "°C"
        state: >
          {{ (
            states('sensor.zwave_kitchen_temperature')|float +
            states('sensor.zwave_living_room_temperature')|float +
            states('sensor.zwave_bedroom_temperature')|float
          ) / 3 | round(1) }}

      - name: "Minimum Risk Zone Temperature"
        unit_of_measurement: "°C"
        state: >
          {{
            [
              states('sensor.zwave_basement_temperature')|float,
              states('sensor.zwave_garage_temperature')|float,
              states('sensor.zwave_outer_room_temperature')|float
            ] | min | round(1)
          }}

automation:
  - alias: "Frost Protection Alert"
    trigger:
      platform: numeric_state
      entity_id: sensor.minimum_risk_zone_temperature
      below: 5
    action:
      - service: notify.mobile_app_your_phone
        data:
          message: "Frost warning! Coldest risk zone at {{ states('sensor.minimum_risk_zone_temperature') }}°C."
          priority: high
      - service: switch.turn_on
        target:
          entity_id: switch.frost_protection_heater

---

3. Dynamic Circadian Lighting with adaptive-lighting

The Problem: In northern Norway, daylight hours swing from 24/7 to near-zero. Static “warm white” light in the evening can disrupt your circadian rhythm. Harsh blue light during a dark winter afternoon isn’t ideal. 

The Solution: The community darling adaptive-lighting integration dynamically adjusts your smart lights’ colour temperature. It also modifies brightness to follow the natural solar pattern for your exact location.

How it Works:

1. You install adaptive-lighting via HACS.
2. Configure it for your HA latitude/longitude. It calculates sunrise, sunset, and solar angles.
3. Set your “daytime” colour temp (e.g., 5000K) and “nighttime” temp (e.g., 2700K). The integration smoothly transitions between them throughout the day.
4. It can also adapt to cloudy days (using a weather integration) and even your personal sleep/wake times.

Why it’s Perfect in Norway: During the polar night, it provides a subtle, artificial “daylight” cue. During the midnight sun period, it helps you wind down. It shifts to warmer tones late in the evening, even if the sun is still up. It’s a silent champion for combating Seasonal Affective Disorder (SAD).

Configuration (YAML in configuration.yaml):

adaptive_lighting:
  - name: "Living Room Lights"
    lights:
      - light.living_room_lamp_1
      - light.living_room_lamp_2
    min_brightness: 10 %
    max_brightness: 100 %
    min_color_temp: 2700  # Warmest (Kelvin)
    max_color_temp: 5000  # Coolest (Kelvin)
    # Take local weather into account
    take_preferable_weather_into_account: true
    # Only adapt when we're 'home'
    only_turn_on_light: true
    # Ignore during the day if we have real sunlight (via a window sensor)
    ignore_lights_off: "{{ is_state('binary_sensor.window_sunlight', 'on') }}"

No manual automations needed! The integration handles the transitions automatically based on your configured schedule and conditions.

---

4. Granular Energy Monitoring with Mosquitto & Self-Hosting-Guide

The Problem: Your smart meter provides aggregate data. You can’t tell if the electric radiator causes your 5 kWh spike at 6 PM. Alternatively, it might be the hot water heater. 

The Solution: Use an Mosquitto Broker add-on. This is the industry-standard MQTT broker. It collects data from individual, circuit-level energy monitors. These monitors include a Shelly EM or a custom ESPHome setup and the system routes this data effectively. Combine this with principles from the Self-Hosting-Guide project. This will enable you to run HA reliably. Mosquitto works effectively on a low-power device like an Intel NUC or a Raspberry Pi 5.

How it Works:

1. Mosquitto runs as an HA add-on, acting as a central message hub.
2. Your energy monitors publish their readings (power in W, energy in kWh) to specific MQTT topics.
3. HA subscribes to these topics via the MQTT integration, creating separate sensor entities for each circuit.
4. You can now build automations and dashboards that see exactly which device is using power.

Why it’s Perfect in Norway: Electricity prices often exceed 3 NOK/kWh. Identifying a faulty appliance is critical. It is also important to recognize an inefficient heater. You can automate turning off non-essential loads during high-price periods (if on a time-of-use tariff).

Example (Node-RED Flow for Real-Time Cost Alert):

• Trigger: mqtt in node listening to energy/water_heater/power.
• Function Node: Calculate cost: msg.payload = (msg.payload / 1000) * current_price_per_kwh; (Fetch current_price_per_kwh from a Nord Pool sensor).
• Switch Node: if power_cost > 5 NOK/hour.
• Action: Send Telegram/notification: “Water heater is costing ⚠️ msg.payload NOK/hour. Consider turning off.”
• (See the Self-Hosting-Guide for best practices on securing your Mosquitto broker with username/password and TLS).

---

5. Historical Insight & Anomaly Detection with mini-graph-card

The Problem: Raw sensor history in the HA frontend is functional but ugly. You need to spot trends: “Is my indoor humidity consistently above 60% in winter?” or “Did that new heat pump actually lower my daily kWh?” 

The Solution: Use the fantastic mini-graph-card (install via HACS) to create beautiful, customizable graphs. These graphs combine multiple sensors, apply moving averages, and highlight anomalies. It turns HA’s recorder database into a powerful analytics tool.

How it Works:

1. Install mini-graph-card.
2. Create a card-mod or dashboard view using its extensive YAML configuration.
3. Graph multiple entities: e.g., sensor.outdoor_temperature vs. sensor.indoor_average_temp vs. sensor.heating_power_consumption.
4. Use its type: statistics to show daily averages, or type: markdown to write custom insights below the chart.

Why it’s Perfect in Norway: Visualize the strong connection between outdoor temperature and your heating energy use. Temperatures can drop to -30°C. Prove the ROI of that insulation job or heat pump. During a cold snap, you can see exactly when your system kicked in.

Example (mini-graph-card YAML in a dashboard):

type: custom:mini-graph-card
title: "Winter Energy & Temp Analysis"
entities:
  - entity: sensor.power_consumption_total
    name: "Total Usage (kWh)"
    color: "#ff9966"
  - entity: sensor.outdoor_temperature
    name: "Outside (°C)"
    color: "#3366ff"
  - entity: sensor.indoor_thermal_comfort
    name: "Inside Avg (°C)"
    color: "#ff3333"
hours_to_show: 168  # One week
smooth: true
show:
  - labels
  - state
  - extrema
  - average
  - name
  - icon
  - state_time

This single card instantly shows you the inverse relationship between outside temperature (blue) and your energy use (orange). It also shows how well your indoor temperature (red) is held stable.

---

Conclusion: From Automation to Intuition

These five ideas move beyond simple triggers. They leverage local, reliable hardware (Z-Wave, Eufy). Their robust infrastructure (Mosquitto) and powerful community projects (adaptive-lighting, mini-graph-card) solve real pain points. These include security during dark months, preventing frozen pipes, and managing circadian health. They also work on slashing energy bills and making data-driven decisions.

Start with one. Integrate your Eufy sensors or deploy a Z-Wave multiset. The beauty of Home Assistant is that these automations don’t exist in silos. Your sensor.minimum_risk_zone_temperature from Automation #2 can feed into your energy dashboard. In Automation #5, and your adaptive-lighting can be disabled when your presence simulation from Automation #1 is running. This is the power of a truly integrated Norwegian smart home.