Clever Automations on Smart Home? Sure — But Secure!

5 Home Assistant Automations That Save Energy

Thu, 20 Aug 2026 00:00:00 +0000

My router, speakers, AV receiver, and printer used to draw a combined 76 watts while doing nothing. If they ran around the clock, that would cost almost €180 per year at my electricity rate. This is where automations help me: not through one spectacular trick, but by preventing small amounts of wasted energy every day.

Here are five solutions from my actual home. Four reliably reduce my energy costs. The fifth sounded sensible but provided no benefit with my heat pump, so I removed it again.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

1. Automatically switch off standby power hogs

My home currently draws around 55 watts of base load when idle. This includes devices that need to remain reachable for the smart home, such as Shelly modules, sensors, and my home server. I consciously accept that consumption.

Several other devices, however, used to stay on even when nobody needed them:

Device	Power	Annual cost if always on
FRITZ!Box router	16 W	almost €40
Five Sonos speakers	35 W	over €80
AV receiver	15 W	around €35
Printer	10 W	around €24

Together, these examples add up to 76 watts. My actual savings are lower than the theoretical €180 because I do not keep the devices off permanently. Home Assistant simply makes sure they are off whenever I do not need them.

When I leave the apartment, I long-press the hallway light switch. This deliberate “I’m leaving” signal switches off Sonos, the receiver, and the printer. The manual trigger is intentional: for this use case, I prefer an unambiguous button press over presence detection that occasionally gets it wrong.

I also switch off the FRITZ!Box at night. My smart home continues to run locally without internet access. I explain why local operation matters in Home Assistant A–Z: O for Offline.

There is a small downside: the Sonos speakers need about a minute after power-up, while the router takes roughly two minutes before everything is available again.

2. Run large loads on solar power

If you have solar panels, flexible high-power appliances should run whenever enough of your own electricity is available. In my home, this mainly applies to the washing machine and electric car.

My washing machine is connected to Home Assistant through Home Connect. In the morning, I load it, select a program, and enable remote start. Once around 2.5 kilowatts of surplus solar power are available, Home Assistant starts the machine automatically.

The car follows the same principle. My Heidelberg Energy Control wallbox is connected to the solar system through Home Assistant and evcc. The Cupra Tavascan charges primarily on surplus solar power unless a defined minimum state of charge takes priority. Of the roughly 3,500 kilowatt-hours the car uses each year, about 1,500 kilowatt-hours come from my own roof despite my relatively small solar array.

3. Get reminded to ventilate efficiently

Leaving a window open for too long wastes heating energy in winter. With a heat pump, that directly becomes additional electricity consumption. I therefore monitor the windows I regularly open using six Homematic contact sensors. The outdoor temperature comes from my heat pump sensor via Modbus.

My simple rule, deliberately tailored to my home, is:

Below 5 °C: send a reminder after 5 minutes
Between 5 and 15 °C: use the temperature as the number of minutes
Above 15 °C: do not send a reminder

If a window remains open beyond that limit, the Home Assistant app sends a push notification. This prevents forgotten windows without creating unnecessary alerts during mild weather. These values are not a universal ventilation formula; they are thresholds that work well for my building.

Bonus: Automate the electricity price too

Automations can reduce consumption or shift it to times when your own solar power is available. Another factor is the price per kilowatt-hour. During my most recent provider switch, I saved 5 cents per kilowatt-hour and received an additional €250 switching bonus.

The remind.me switching service checks once a year for the best suitable electricity, gas, or heat-pump tariff and prepares the switch. New-customer bonuses are included, and you have the right to veto every switch.

👉 Learn more about the remind.me switching service

4. Why I removed night setback

Turning down the heating at night sounds like an obvious way to save energy. Whether it works depends on the building, heat emitters, heat source, and control system.

In a poorly insulated older building with conventional radiators, night setback can indeed save energy. With my combination of a heat pump, underfloor heating, and a high-mass screed floor, however, the room temperature barely drops overnight. If the controller then catches up in the morning using a higher flow temperature, that less efficient operation can consume the small theoretical saving.

Night setback provided no measurable benefit in my setup, so I removed the automation. The better rule is not to apply it blindly, but to compare actual consumption over equivalent periods.

5. Shutters save energy in summer and winter

My shutters close automatically based on the position of the sun. This saves energy in two ways:

In summer, they keep solar heat outside, reducing the work required from an air conditioner.
In winter, closed shutters add another layer in front of the windows at night, reducing heat loss and the amount of electricity required by the heat pump.

I explain how to create sun-dependent shading with Home Assistant blueprints in Home Assistant A–Z: J for Shutters.

Conclusion

None of these automations is a revolution on its own. Together, however, they prevent unnecessary standby consumption, make better use of solar power, and reduce wasted heating or cooling energy. Once configured, most of them run almost entirely by themselves.

Night setback is the important counterexample: an automation does not automatically save energy just because it is commonly presented as an energy-saving tip. What matters is what it actually does in your home.

Which smart home automation saves the most energy for you – and which supposed energy-saving trick did you switch off again?

The Automation You Never Want – But Must Have

Wed, 29 Apr 2026 18:00:00 +0200

My first video about the XSense smoke detectors surprised me a little. Not because of the numbers – but because of one particular moment in the video.

I’d briefly mentioned what I’d built for the Home Assistant integration: when a smoke detector goes off, all lights come on, all blinds go up, and I get a push notification on my phone. Just a quick aside because it fit the topic. But those few seconds apparently triggered something – in the comments, and at XSense itself.

How this video came about

Shortly after publishing the first video, XSense reached out. I explained the blind and automatic light idea in an email – and they found it so interesting that they asked me to make a detailed video about it. Show exactly how it’s built. What happens step by step. And why.

So here it is.

Why this automation matters more than it sounds

I’ll say it plainly: this isn’t a cool toy. This is an automation I hope you never need. But if you do need it, every second counts.

In a fire, two things rob you of the precious time to escape: disorientation and panic. Someone woken from sleep in the middle of the night often doesn’t immediately know where they are, where the door is, how to get out. And if everything is dark and the blinds are down – that’s a serious problem.

A well-designed automation can help counter exactly that. Not as a replacement for smoke detectors, escape route plans or fire extinguishers – but as one more layer that works silently and reliably when it matters.

What’s in the video

I build the complete automation live – from the MQTT entity of the smoke detector to the finished, tested automation chain in Home Assistant.

What happens when an alarm is triggered:

Push notification to your smartphone – immediately, even if you’re not home
All lights come on – escape routes become visible, no one stumbles in the dark
All blinds go up – windows become accessible as emergency exits, firefighters can see what’s happening from outside

I also show what to watch out for when building it so the automation works when it actually matters – including when the internet is down or Home Assistant just restarted.

And I explain why I deliberately didn’t add an automatic emergency call – it sounds like a good idea, but in practice it isn’t.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

What have you already automated for emergencies at home? Write it in the comments – I’m genuinely curious how you’ve solved this.

The devices from the video

The XSense system the automation is built on:

6-pack starter set + base station (affiliate link): 👉 XS01-M 6-pack at XSense
12-pack + base station (affiliate link): 👉 XS01-M 12-pack at XSense
Discount code: AFQ3XSENSE → 12% off your entire order (X-Sense shop only, valid until September 30, 2026). Combinable with official website deals where applicable – during sitewide promotions the system automatically applies the lowest price (the code may then not apply at checkout), so just check the final price at checkout.
Alternatively via Amazon: 👉 XSense smoke detectors on Amazon (affiliate link)

This video was made in collaboration with XSense. Affiliate links: the price stays the same for you, but you support the work on my channel.

5 New Automation Mistakes in Home Assistant

Wed, 18 Mar 2026 00:00:00 +0200

It was a perfectly normal evening. I built an automation, started it — and it simply didn’t do what it was supposed to. No error in the logs. No red bar. Just: nothing.

After twenty minutes of searching, I found the mistake. And then something became clear to me: That wasn’t a one-off slip. That was a pattern.

My first video on the 5 most common automation mistakes was a hit back then — the comments went wild. And many of you wrote: “I knew all of these and still do them anyway.” I get it. I really do.

Since then, quite a bit has changed in Home Assistant. New features, new possibilities — and a whole new category of traps to fall into. Trigger IDs, for example. Or AI-generated automations that look so plausibly correct — and then aren’t.

I’ve picked out five of them. Five new mistakes I had to learn the hard way myself — and that I keep seeing when talking to the community. Some are insidious because the mistake only surfaces weeks later. One of them costs you all the progress of a running automation — at exactly the moment you least expect it.

Five mistakes that sound more harmless than they are

Mistake 1: The Trigger ID Trap

Trigger IDs are one of the features that have genuinely upgraded Home Assistant in recent years. You can finally consolidate multiple triggers in one automation and still tell them apart. Practical, elegant, modern.

And that’s exactly why this trap is so sneaky. Anyone who’s discovered the feature wants to use it for everything. Ten triggers, twelve conditions, a huge choose block — and at some point, actions fire that shouldn’t be firing at all. No error in the logs. Everything runs. Just wrong.

How to use trigger IDs properly — and where the line is — I show in the video.

Mistake 2: The light burns even when the sun’s still out

You built an automation: lights on at 6 PM. In October, that’s perfect. In March, the lamp is on while it’s still broad daylight outside. In December, you’ve been sitting in the dark for an hour.

Hard-coded times feel right when you set them up — and they get their revenge for the rest of the year. Most of us have at least one such automation hidden somewhere. Sometimes even several.

The good news: Home Assistant has everything you need to solve this permanently. What exactly — you’ll see in the video.

Mistake 3: The silent total loss

This is the mistake that surprised me most — and at the same time the one most people completely underestimate. You build an automation with a long wait action. Everything runs. At some point you apply an update. Home Assistant restarts.

And your automation? It remembers nothing. No hint, no log, no error message. The progress is simply gone. That can mean: a reminder is never sent. A lamp stays on. A door remains unnoticed open.

There’s an elegant solution for this — and it’s simpler than you’d think. But it requires a change of thinking. I explain how in the video.

Mistake 4: The script that silently refuses

Anyone who knows automation modes feels confident. Single, Restart, Parallel, Queue — that’s clear. But now here’s the trick question: Are you also keeping an eye on the modes of your scripts?

In the default mode Single, if a script is already running and gets called again, absolutely nothing happens. No error message. The script is simply ignored. Depending on your use case, your system then runs silently into the void — and you don’t know why.

Mistake 5: The automation that looks like a good idea

We use AI. That’s normal, that’s sensible, that’s fast. ChatGPT, Gemini, the built-in Home Assistant assistant — they can all deliver a first draft of an automation in seconds. And it looks good. Really good. Structured, plausible, commented.

The problem: ancient syntax from three-year-old training data. Entities that don’t even exist in your installation. Logic errors that only surface when they’ve already surfaced. AI code doesn’t check itself — you have to do that.

In the video, I show a real example and explain where you need to look especially carefully.

All five mistakes — with screenshots, real examples, and a look inside the automation editor — are in the video:

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

Write in the comments afterwards which mistake got you the most — just the number, e.g. “Mistake 3”. That’s how I know what’s really on your mind.

→ If you want to secure your automations, the next step is security: Securing Home Assistant – 5 mistakes to avoid in your smart home

Home Assistant A-Z: O is for Offline – No Internet?

Sun, 04 Jan 2026 00:00:00 +0200

A Confession at the Start of 2026

Time for a confession: I turn off my Fritzbox every night – completely on purpose! And yes, my smart home keeps running anyway. It wasn’t always like that and took some work to get right. But why is it even worth checking whether your smart home still works offline?

The answer is simpler than you might think. Watch the video and find out why you should review your automations – even if you’d never dream of switching off your own router!

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

Why Offline Functionality Matters

You don’t have to be as radical as me and deliberately cut your internet connection. Still, it’s worth understanding when your smart home works offline and where it might silently fail.

Internet Outages Are Not Rare

You won’t always be offline by choice. It happens like this too:

The internet goes down (ISP outage, broken router)
Certain servers become unreachable (cloud services down)
Wi-Fi issues in individual rooms

In all of these cases, your smart home should reliably keep running for core functions!

The Smart Bed Example

A particularly striking (or alarming?) example: a smart bed costing $3,000. When Amazon’s cloud servers went down, users had a serious problem:

❌ The sleeping position could no longer be adjusted
❌ Temperature regulation stopped working
❌ Users were stuck sleeping in uncomfortable positions or sweating through the night

In practice, it doesn’t matter whether Amazon’s server has issues or your internet connection does. The effect would be the same either way.

A Real-World Example From My Smart Home

Let me show you with a concrete example from my own smart home. In the video you can see the automation live, and I walk you through every step in detail!

The Window Reminder Automation

This automation reminds me when I leave a window open in cold outdoor temperatures, to prevent the apartment from cooling down unnecessarily.

Here’s how it works:

Trigger: One of several windows is opened
Condition: Outdoor temperature is below 18°C
Action: After a set amount of time, a reminder to close the window

The Problem With Cloud-Based Sensors

Originally I was relying on my weather sensor – specifically the temperature from a weather forecast integration. If you watch the history in the video, you’ll spot the problem immediately:

At night the sensor was unavailable (which makes sense – I’m cutting the internet, after all).

This meant:

The automation cannot evaluate the condition
The condition is treated as “false”
The automation stops and doesn’t continue
I get no warning, even if it’s freezing outside!

The Fix: Use Local Sensors

The solution was straightforward: I have a heat pump in the basement with an outdoor temperature sensor connected to Home Assistant via MQTT.

Advantages: ✅ The sensor is always available (local via MQTT)
✅ No dependency on internet or cloud
✅ Automation runs reliably even at night

In the video I show you exactly how I updated the conditions!

Resilient Automations With Fallback Values

But simply swapping the sensor isn’t enough. You also need to handle failures gracefully.

Float Conversion With a Default Value

In the automation I check:

1

{{ states('sensor.waermepumpe_aussentemperatur') | float(default='none') }}

What’s happening here?

The sensor value is converted to a floating-point number
If that fails (e.g. sensor unavailable), none is returned instead
This lets me react in a controlled way rather than having the automation abort

Safety Through Fallback Logic

My final condition:

1

Is the temperature = none OR below 18°C?

In both cases the automation should continue running!

Why? Better to be warned once too often than once too few. If I can’t read the value, I assume the worst case: it might be cold, so warn me anyway!

In the video you can see the complete logic step by step!

Second Example: Variable Wait Time

In the same automation I use a variable wait time depending on outdoor temperature:

10°C outside → window can be open for up to 10 minutes before a warning
5°C outside → window can be open for up to 5 minutes before a warning
Below 5°C → minimum wait time of 5 minutes

Here too I had originally used the weather sensor – with the same problems!

The Resilient Solution

1

{{ [states('sensor.waermepumpe_aussentemperatur') | float(default=0), 5] | max }}

What does this do?

Temperature is read and converted to float
On failure: default value of 0
Take the maximum of the temperature and 5
Result: At least 5 minutes, up to 18 minutes (when the condition fires)

This way the automation works reliably even when a sensor is unavailable!

Want to see the exact implementation? Watch the video – I show you the automation live inside Home Assistant!

How Do You Identify Offline-Dependent Integrations?

An important question: How do you even know which integrations require internet access?

In the video I show you:

Weather integration (requires internet):

Home Assistant explicitly labels it as “Cloud Polling” or similar
Not available without internet

MQTT integration (no internet needed):

Connects to a local MQTT broker
Works completely offline

Tip: Take a look at your integrations in Settings. Home Assistant usually marks cloud-based integrations clearly!

Why I Turn Off the Fritzbox at Night

In case you’re wondering why I do this at all:

My reasons:

Save standby power: Around €10–15 per year
Sustainability: I simply don’t need internet at night
Testing smart home resilience: Forces clean solutions
Smartphone falls back to LTE: I remain reachable regardless

It took some thought to get everything in the smart home working properly. But now I’m happy with it!

Important: You don’t have to do the same. This is a personal choice. The lessons from it, however, apply to everyone!

My Three Most Important Tips for You

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

You don’t need to turn off your router. But these three things are worth keeping in mind:

1. Make Core Functions Work Offline

Make sure these functions work without internet:

✅ Lights
✅ Blinds and shutters
✅ Heating
✅ Security functions

These are essential to your home. They must not depend on an internet connection!

2. Comfort Functions Can Be Dependent

Comfort functions that you don’t strictly need can rely on internet services:

Weather forecasts on the dashboard
Voice assistants
Cloud notifications
External data sources

That’s perfectly fine – as long as the core functions keep working!

3. Review Your Automations for Resilience

Go through your automations:

Which sensors are used?
What happens if a sensor becomes unavailable?
Are there sensible fallback values?
Does the automation abort on errors or continue in a controlled way?

This is an improvement you won’t notice every day. But when it matters, you’ll be grateful your smart home still runs reliably!

Conclusion: Resilience Is Not Rocket Science

As you can see, resilient automations are not rocket science. All it takes is:

Awareness of which sensors are available offline
Controlled error handling with default values
Sensible fallback logic instead of automation aborts

Watch the video to see everything live and explained step by step. Once you’ve gone through your own automations, I’d love to hear what you found!

Feel free to write your thoughts in the comments below the video or this article.

Home Assistant A-Z: N is for Night Mode

Sun, 28 Dec 2025 00:00:00 +0000

Welcome to the A-Z Series: N is for Night Mode

In today’s episode of the Home Assistant A-Z Series we tackle a topic that every smart home user knows: How do you stop your hallway from lighting up like an airport runway in the middle of the night?

The answer is: night mode! But not just any night mode – today I’ll show you how to use a central Smart Home status to intelligently control all your automations. From dimmed night lights to closed blinds to gentle radio as you drift off to sleep!

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

The Problem: Being Blinded at Night

Sound familiar? You wake up in the middle of the night, need a quick bathroom trip, step into the hallway – and BAM! Full brightness hits you square in the face. Your eyes need five minutes to recover. Any chance of relaxing back to sleep is gone.

It doesn’t have to be this way! With an intelligent night mode you can:

✅ Use dimmed night lights instead of full brightness
✅ Navigate without being blinded
✅ Fall back asleep quickly after your midnight trip
✅ Automatically adapt multiple rooms (hallway, bathroom, etc.)

And the best part: All of this works automatically, without you having to manually switch anything!

In the video I show you the problem and the solution live!

The Secret: A Central Smart Home Status

Many Home Assistant users build complicated automations with dozens of conditions. “If the time is between 10 PM and 6 AM AND nobody is in the living room AND…” – it quickly becomes a mess.

My solution: A central Smart Home status that reflects the current state of your entire home!

What is a Smart Home Status?

Talking to other smart home users, I keep noticing: many people don’t bother maintaining a status in their smart home. Yet it is incredibly useful!

A status is simply a Helper (Input Select) that represents the current state of your smart home.

My four states:

Present – Normal operation, everyone is home
Night – Someone has gone to bed
Away – Nobody home
Vacation – Extended absence

That’s it! These four states are enough to keep all my automations running appropriately.

In the video you can see the status live on my dashboard, including the history of the last 24 hours!

Why is a Status so Powerful?

The big advantage: your automations become much simpler!

Instead of:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10


condition:
 - condition: time
 after: "22:00:00"
 before: "06:00:00"
 - condition: state
 entity_id: group.all_persons
 state: home
 - condition: state
 entity_id: media_player.wohnzimmer
 state: 'off'

You simply write:

1
2
3
4


condition:
 - condition: state
 entity_id: input_select.smart_home_status
 state: 'Nacht'

Much more readable, maintainable, and flexible!

Live: My Smart Home Status

Let me show you my status live. I have a helper called “Smart Home Status”.

Currently set to: “Anwesend” (of course – I’m recording a video right now!)

In the history of the last 24 hours you can see:

🟢 Present (daytime)
🌙 Night (from roughly 10:30 PM to 6:30 AM)
🟢 Present (after waking up)

The status is set automatically and moves through different phases over the course of a normal day.

Make sure to watch the dashboard in the video – the visualization makes it even clearer!

How is the Status Set Automatically?

Of course I don’t want to open the dashboard every evening and manually click “Night”. That would be absurd!

That’s why I have various automations, all with the goal of changing the status.

Trigger 1: Zigbee Button by the Bed

The most important automation: I have a Zigbee button next to my bed (e.g. an Aqara Wireless Mini Switch).

When I press it:

Status switches to “Night”
An automation cascade is triggered (more on that in a moment!)

This is perfect, because the button press marks the exact moment when I go to bed – not some arbitrary time, but precisely when I want to sleep.

In the video I show you the button and the automation!

Trigger 2: Alarm in the Morning

In the morning, when my alarm goes off, an automation lifts the Night status again:

1
2
3
4
5
6
7
8
9


trigger:
 - platform: time
 at: input_datetime.wecker_time
action:
 - service: input_select.select_option
 target:
 entity_id: input_select.smart_home_status
 data:
 option: 'Anwesend'

The entire smart home wakes up along with you!

Trigger 3: Absence

When all household members leave home, the status switches to “Away”:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11


trigger:
 - platform: state
 entity_id: group.all_persons
 to: 'not_home'
 for: "00:05:00"
action:
 - service: input_select.select_option
 target:
 entity_id: input_select.smart_home_status
 data:
 option: 'Abwesend'

Check out all the trigger automations in the video!

The Automation Cascade When Night Mode Activates

When the status switches to “Night”, it doesn’t just trigger one thing – it sets off a whole cascade of automations!

What Happens Automatically:

1. Blinds close

All blinds in the bedroom – and possibly the living room – close automatically:

1
2
3
4
5
6
7
8
9


trigger:
 - platform: state
 entity_id: input_select.smart_home_status
 to: 'Nacht'
action:
 - service: cover.close_cover
 target:
 entity_id:
 - cover.rollladen_schlafzimmer

2. Bedroom light dims

The bedroom light is dimmed to a very low brightness and then fades out slowly over a 10-minute ramp:

1
2
3
4
5
6


- service: light.turn_on
 target:
 entity_id: light.schlafzimmer
 data:
 brightness: 10
 transition: 600 # 10 Minuten

3. Radio plays softly

A radio turns on at low volume, giving me some entertainment as I fall asleep:

1
2
3
4
5
6
7
8


- service: media_player.turn_on
 target:
 entity_id: media_player.schlafzimmer
- service: media_player.volume_set
 target:
 entity_id: media_player.schlafzimmer
 data:
 volume_level: 0.15

All of this happens with a single button press! Simple, elegant, reliable.

In the video I show you the complete automations in detail!

The Core Feature: Night Light Instead of Main Light

Now here’s the real trick of night mode: intelligent light control!

My Hallway Setup

In my hallway I have two different lights:

Main light (bright ceiling lamp via Shelly)
LED strip on a built-in cabinet (dimmed as a night light)

The goal: During the day the main light should come on; at night, only the dimmed night light!

The Night Light Automation

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15


alias: Flur Nachtlicht bei Bewegung
trigger:
 - platform: state
 entity_id: binary_sensor.bewegungsmelder_flur
 to: 'on'
condition:
 - condition: state
 entity_id: input_select.smart_home_status
 state: 'Nacht'
action:
 - service: light.turn_on
 target:
 entity_id: light.flur_nachtlicht
 data:
 brightness: 30

The condition is key: The night light only activates when the status is “Night”!

The Main Light Automation

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15


alias: Flur Hauptlicht bei Bewegung
trigger:
 - platform: state
 entity_id: binary_sensor.bewegungsmelder_flur
 to: 'on'
condition:
 - condition: not
 conditions:
 - condition: state
 entity_id: input_select.smart_home_status
 state: 'Nacht'
action:
 - service: light.turn_on
 target:
 entity_id: light.flur_hauptlicht

Here the condition is reversed: The main light only turns on when the status is not “Night”!

This is how I avoid being blinded when I step into the hallway at night!

In the video you can see both automations live in action!

The Bathroom Has Night Mode Too

I’ve applied the same principle in the bathroom as well:

At night: Dimmed night light (around 20% brightness)
During the day: Full brightness

This gives me a safe path from bed to bathroom and back, gently lit whenever the status is “Night”.

It makes those midnight bathroom trips so much more pleasant!

Why Not Just Use a Time Condition?

Good question! You could simply say: “Between 10 PM and 6 AM, use dimmed lighting.”

But: What if you stay up late on the weekend? Or go to bed early because you’re sick? Or get up at 3 AM and can’t fall back asleep?

With the status-based approach none of that is a problem:

✅ Adapts flexibly to your actual sleep schedule
✅ No rigid time window
✅ Manual override possible (press the button even if it’s only 9 PM)

In the video I explain why the status approach beats time conditions!

Morning: Alarm Cancels Night Status

When my alarm goes off in the morning, the “Night” state is automatically lifted:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10


alias: Wecker - Status auf Anwesend
trigger:
 - platform: time
 at: input_datetime.wecker_time
action:
 - service: input_select.select_option
 target:
 entity_id: input_select.smart_home_status
 data:
 option: 'Anwesend'

The entire smart home wakes up!

When I then step into the hallway I get an appropriately wake-you-up light – no longer the dimmed night light, but full brightness.

Perfect for starting the day!

More Use Cases for the Status

The Smart Home status isn’t just useful for night mode! Here are a few more ideas:

Status “Away”

When nobody is home:

🚫 Turn down the heating
🚫 No motion-triggered lights
✅ Activate presence simulation
✅ Arm the alarm

Status “Vacation”

Extended absence:

🌅 Blinds simulate a normal daily routine
💡 Lights turn on and off at “realistic” times
🌡️ Heating set to frost protection
📧 Important notifications via email instead of push

Additional Status Ideas

You can of course define your own states:

“Party mode” – Special lighting, music integration
“Sick” – Higher heating, blinds closed, more quiet
“Work” – Home office mode with notification silencing
“Movie” – Dim lights, optimize TV settings

The possibilities are endless!

How to Set Up the Status

Convinced and ready to set up your own Smart Home status? Here’s how:

Step 1: Create the Input Select Helper

Go to: Settings → Devices & Services → Helpers

Click “Add Helper” and choose “Dropdown”

Settings:

Name: Smart Home Status
Icon: mdi:home-assistant
Options:
- Anwesend
- Nacht
- Abwesend
- Urlaub

Save! You now have input_select.smart_home_status

Step 2: Create Status Automations

Create automations that set the status:

Activate night mode:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13


alias: Nachtmodus aktivieren
trigger:
 - platform: event
 event_type: zha_event
 event_data:
 device_id: 'dein_zigbee_taster_id'
 command: single
action:
 - service: input_select.select_option
 target:
 entity_id: input_select.smart_home_status
 data:
 option: 'Nacht'

Wake up:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10


alias: Aufwachen - Nachtmodus beenden
trigger:
 - platform: time
 at: '06:30:00'
action:
 - service: input_select.select_option
 target:
 entity_id: input_select.smart_home_status
 data:
 option: 'Anwesend'

Step 3: Use the Status as a Condition in Your Automations

Now you can use the status as a condition in all your automations:

1
2
3
4


condition:
 - condition: state
 entity_id: input_select.smart_home_status
 state: 'Nacht'

Done! You now have a working Smart Home status.

In the video I walk you through all the steps in detail!

Tips and Tricks

A few valuable tips from my experience:

Tip 1: Place the Status Prominently on Your Dashboard

The status should be clearly visible so you always know what state your smart home is in.

Recommendation: On the home page at the very top, as a badge or large tile.

Tip 2: Allow Manual Overrides

Sometimes you want to change the status manually. Make sure the dashboard element is not read-only!

Tip 3: Keep the History

Enable long-term statistics for the status helper so you can trace how your smart home behaves over time.

Tip 4: Logging for Debugging

During development: log all status changes:

1
2
3
4


- service: logbook.log
 data:
 name: Smart Home Status
 message: "Status gewechselt zu {{ states('input_select.smart_home_status') }}"

This lets you see in the logbook when and why the status changed.

In the video I go into these tips in more detail!

Avoiding Common Pitfalls

A few typical mistakes I made early on:

Mistake 1: Too Many States

I started with 8 different states. It quickly became unmanageable. 4–5 states are plenty!

Mistake 2: Forgetting to Reset the Status

If the status is stuck on “Night” and you forget to reset it in the morning, your automations will run incorrectly all day!

Solution: Multiple triggers for resetting (alarm, time, manual light control)

Mistake 3: No Fallback Logic

What happens if the button breaks? Always have a second way to set the status (e.g. dashboard, time-based backup trigger)

Conclusion: Maintaining a Status is Worth It!

There really is nothing more to it than that! A simple helper with 4 states, a few automations to set the status, and then conditions in your relevant automations.

But the impact is enormous:

✅ Simpler automations (fewer complex conditions)
✅ Better readability (clear what happens when)
✅ Centralized logic (change the status instead of dozens of automations)
✅ Flexibility (new automations reuse the same status)

A status is useful for many things – not just night mode!

Make sure to watch the full video – you’ll see everything in action and I go into even more depth there!

Your Experiences?

Do you use a Smart Home status?

Home Assistant A-Z: L is for Light – Simple to Creative

Sun, 14 Dec 2025 00:00:00 +0000

Welcome to the A-Z Series: L is for Light

In today’s episode of the Home Assistant A-Z Series we’re tackling the absolute classic for beginners: light! For many people, their first lighting automation is the magical moment when an idea becomes a real smart home. But there’s so much more to it than just on and off!

Today I’ll show you how I use light in my smart home – from simple motion-sensor automations to gentle wake-up lights and creative visual reminders. Let yourself be inspired!

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

How I Control My Lights: The Hardware

Before we get to the exciting automations, let me show you which hardware I use for my lighting control. Spoiler: it’s a colourful mix – and that’s exactly what makes Home Assistant so flexible!

Shelly Modules: The In-Wall Solution

The bulk of my lighting runs through Shelly modules (e.g. the Shelly Plus 1 PM* – also at OBI*) that I’ve fitted behind existing wall switches. There are several advantages:

✅ The existing wall switch still works
✅ Additional control via Home Assistant
✅ Completely local, no cloud required
✅ Affordable retrofit for existing lamps

In my home these cover, among others:

Guest bathroom
Hallway
Bathroom
Dressing room
Storage room

The Shellys are integrated directly into Home Assistant via the Shelly integration and respond instantly – whether I use the physical switch or trigger an automation.

In the video I show you exactly what that looks like in the dashboard!

Philips Hue: Colour and Flexibility

I also have some Philips Hue lights in use, which I control via Zigbee2MQTT. The advantage: no Philips Hue Bridge needed – everything runs through my Zigbee stick!

Where I use Philips Hue:

Bedroom – for the gentle wake-up light (more on that in a moment!)
Terrace – for atmospheric evening lighting

Depending on the model, Hue lights can:

Change white tones (from cool white to warm white)
Display full RGB colours
Dim softly over long periods

In the video you’ll see the difference between the various Hue models live in the dashboard!

ESPHome LED Strip: The DIY Project

My personal highlight is a custom-built LED lamp in the hallway, made from an LED strip with individually addressable LEDs. Control is handled by an ESP32 microcontroller running ESPHome.

What makes it special: the lamp consists of several rings that I can address individually with different colours. I use this for creative automations – more on that shortly!

Make sure to watch the lamp in action in the video – the effects are impressive!

What Can I Do With the Different Lights?

Now it gets interesting: what are the possibilities of the different light types?

Shelly: Simple but Reliable

The Shelly-controlled lights are the simplest in my setup. They can:

✅ Switch on and off

Sounds underwhelming? It is – but that’s exactly what makes them so reliable and fast. For rooms like the bathroom, hallway, or storage room, I don’t need anything more. The main thing is that the light comes on when I need it!

Philips Hue: The Colour Artists

With the Hue lights things get considerably more interesting. Depending on the model they can:

Warm white / cool white lights:

Change colour temperature (from cosy warm white to energising cool white)
Dim brightness continuously
Smooth transitions over minutes or even hours

RGB lights:

Display any colour in the RGB spectrum
Colour-change animations
Combinations of colour and brightness

In the video I show you both variants live in the dashboard – the difference is striking!

ESPHome LED Strip: The All-Rounder

My custom-built LED lamp can do everything Hue can – and more:

Full RGB display for every individual LED
Individual control of separate rings with different colours
Special effects such as running lights, rainbow, or pulsing
Dynamic displays for smart home status

I use this flexibility for the most creative automations – more on that shortly!

The Interesting Automations

Now for the exciting part: what do I actually do with all these lights? Here are my favourite automations!

Motion Sensor + Shelly: The Classic

The simplest and simultaneously most useful automation: light comes on automatically when I enter a room.

How does it work?

Motion sensors distributed throughout the rooms
Trigger: Motion detected
Action: Switch on Shelly light
Timeout: Automatically switch off after X minutes without motion

Where I use this:

Hallway
Storage room
Dressing room
Guest bathroom

Sounds trivial, but it’s incredibly practical! You come in from the car with your hands full and don’t have to feel for a light switch. The light is simply already on.

In the video I show you the automation and how it responds live!

Wake-Up Light: A Gentle Start to the Day

This is where it gets more interesting: my Philips Hue lights in the bedroom serve as a gentle wake-up light.

The problem: A normal alarm clock tears you brutally out of sleep. With light, it’s so much gentler!

How I implement it:

Trigger: Wake-up time (weekdays only)
Action: Gradually dim lights up over 20 minutes
Starting point: Very warm, dimmed light (simulates morning sun)
End point: Bright, cooler light (gently wakes you up)

The trick: Home Assistant can slowly brighten lights using a transition parameter. This means the light continuously changes brightness and colour temperature over 20 minutes!

Additional feature: At the same time I also switch on the radio and slowly increase the volume. The perfect start to the day!

Make sure to look at the automation code in the video – I’ll show you the transition parameter!

I use the custom-built LED lamp in the hallway as an intelligent night light:

The idea: When someone needs to use the bathroom at night, the hallway should be subtly lit – but not so bright that you’re fully awake.

How it works:

Motion sensor detects movement in the hallway
Condition: It is between 22:00 and 06:00
Action: LED lamp switches on with very low brightness and warm light
Timeout: Automatically switches off after 2 minutes

The brilliant part: the lamp is bright enough to navigate by, but not so harsh that it wakes you up completely. The perfect compromise!

Bin-Day Reminder: Never Forget Visually Again

Now it gets really creative: I use the individually addressable rings of my LED lamp as a visual reminder for bin collection!

The problem: I regularly forget to put the bin out in time.

The solution: The lamp shows me in colour which bin is being collected tomorrow!

How it works:

Trigger: Afternoon at 16:00
Condition: Check whether a bin is being collected tomorrow
Action: Show a coloured ring on the LED lamp
- 🟢 Green = Food/garden waste bin
- 🟡 Yellow = Recycling/yellow bag
- 🔵 Blue = Paper bin
- ⚫ Black = General waste

Every time I walk through the hallway I see the coloured ring and am reminded. Better than any push notification!

In the video I show you the complete automation and what the lamp looks like when multiple bins need to go out at the same time!

By the way: how I integrate bin collection schedules into Home Assistant is covered in a dedicated article about the bin collection integration. Definitely check it out if you’re interested in that topic!

More Creative Ideas for Light in Home Assistant

You can see: light is so much more than just on and off! Here are a few more ideas I haven’t implemented myself, but which might be interesting for you:

Presence Simulation While on Holiday

Use your smart lights to simulate presence when you’re away:

Lights come on and go off at random times
Different rooms are lit in sequence
Timings oriented around realistic patterns (living room in the evening, bedroom at night)

Alarm Visualisation

If movement is detected in the garden or a window opens while you’re away, lights can:

Flash red as a warning
Alert you acoustically and visually
Act as a deterrent to intruders

Mood Modes

Create different scenes for different situations:

🎬 Movie mode: Dimmed, warm light
🍽️ Dinner mode: Bright, cosy light over the dining table
🎉 Party mode: Colourful colour changes
📚 Reading mode: Bright, neutral white light

Daylight Adaptation

Automatically adjust the colour temperature of your lights to the time of day:

Morning: Cool, energising light
Midday: Neutral white
Evening: Warm, relaxing light (supports your natural sleep rhythm)

Why Light Is the Perfect Entry Point into Home Assistant

If you’re new to Home Assistant: light is the ideal starting point!

Reasons:

Immediate feedback – you see straight away whether your automation is working
Not critical infrastructure – if something goes wrong, it’s not a disaster
Many hardware options – from affordable (Shelly) to comfortable (Hue)
Simple automations – perfect for learning the basics
Plenty of room for creativity – once the basics are in place, you can experiment

In the video I give you even more tips for beginners!

Hardware Recommendations

Want to get started smart? Here are my hardware recommendations based on my own experience:

For Wall Switches: Shelly

Shelly 1 or Shelly 1PM for simple on/off lights
Works with existing switches
Completely locally controllable
Affordable to purchase

For Colour and Comfort: Philips Hue

Zigbee2MQTT instead of a Hue Bridge (saves money and increases flexibility)
White Ambiance for colour temperature control
White and Colour for full RGB control

For Makers: ESPHome

WLED-compatible LED strips with WS2812B LEDs
ESP32 or ESP8266 as controller
ESPHome for easy integration into Home Assistant

Affiliate links to recommended hardware can be found in the video description!

Avoiding Common Pitfalls

From my experience there are a few typical mistakes when getting started with lighting control:

Mistake 1: Too Many Automations for One Light

When multiple automations control the same light, they can conflict with each other. Example: a motion sensor switches the light on, but at the same time another automation wants to switch it off.

Solution: Use conditions in your automations or central logic helpers.

Mistake 2: No Manual Override

It’s annoying when an automation switches the light off while you’re still in the room!

Solution: Build in manual override options, for example via an Input Boolean.

Mistake 3: Motion Sensor in the Wrong Spot

A poorly positioned motion sensor detects you too late – the light stays off.

Solution: Test different positions and pay attention to the detection range of your sensor.

In the video I go into these pitfalls in more detail!

Watch the Video!

I’ve told you a lot, but you’ll understand it best when you see it! In the video I show you:

✅ All lights live in the dashboard
✅ The automations in detail
✅ The custom-built LED lamp in action
✅ What the bin-day reminders look like
✅ The code for the wake-up light

Click the video above and watch it now!

Further Articles and Videos

If you’re interested in the topic of lights and automations:

Never forget the bins again – How I use the bin collection integration
Installing Shelly roller blinds – If you want to learn more about Shelly modules
Blueprints – How to easily import automations

The complete A-Z Series can be found here: Home Assistant A-Z Overview

Home Assistant A-Z: K is for AI – Does AI Belong?

Sun, 07 Dec 2025 00:00:00 +0000

Welcome to the A-Z Series: K is for AI

In today’s episode of our Home Assistant A-Z Series, we tackle a controversial topic: Artificial Intelligence in your Smart Home! AI is everywhere right now – but does it really align with the core principles of Home Assistant? Today I give you 10 reasons why AI actually doesn’t belong in Home Assistant – and at the end I’ll still tell you where AI can make sense.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

The Uncomfortable Truth About AI in Smart Home

Artificial intelligence is the buzzword of the moment. Every manufacturer advertises it, every app wants to be “intelligent.” But let’s be honest: Does your Smart Home really need AI? Or is it just marketing?

Home Assistant was built with clear values: Local control, privacy, independence, and reliability. And this is exactly where the problem with AI models begins. In the video I show you why these two worlds actually don’t fit together – and why that’s actually a good thing!

Reason 1: Cloud Dependency vs. Local Control

The foundation of Home Assistant is local control. Your data stays with you, your system works even without internet. This is one of the main reasons many of us switched to Home Assistant in the first place!

AI models, on the other hand? They run almost always on external cloud servers. Why? Because they need enormous computing power. That’s the complete opposite of what makes Home Assistant special.

In the video I explain why this cloud dependency is not just a philosophical problem, but has real practical disadvantages.

Reason 2: Unpredictability – Smart Homes Need Determinism

Imagine: You come home and sometimes the lights turn on, sometimes not. Or the heating decides today that it’s not that cold after all. Sounds absurd? That’s exactly what happens when you let AI run unchecked in your Smart Home!

AI always works with probabilities. “With 87% probability the mail carrier is at the door” – fine for a notification. But for critical automations? Absolutely not!

When It’s Cold, the Heating Must Come On

A classic example from the video: When the temperature drops below 19 degrees, the heating should kick in. Period. No discussion.

You don’t want an AI model “thinking” about whether it currently makes sense to turn on the heating. You’re cold right now – there’s no time for probability calculations!

Watch the video to see where this difference between deterministic rules and AI probabilities really becomes critical!

Reason 3: Explainability Is Completely Missing

With a classic automation you can precisely trace what happened:

You look at the traces
You see which conditions were met
You find the error and fix it

With AI you only get: “The model decided it was A.” Why? No idea. What can you change? Unclear.

Classic debugging as in software development is simply impossible. In the video I show you why this is a massive problem for the maintainability of your Smart Home.

Reason 4: Hallucinations Are Fatal in Smart Homes

You’ve surely heard of “hallucinations” in AI models – when the AI makes up things that don’t exist. This is an inherent property of AI and cannot be completely eliminated.

AI Cannot Say “I Don’t Know”

AI models have an extremely hard time admitting they don’t know something. Present them with a choice between A or B, and a decision will be made – even if the underlying data isn’t there at all.

In your Smart Home, this can have fatal consequences. In the video I give you concrete examples of where such hallucinations can become truly dangerous.

Reason 5: AI Is in Constant Flux

What works today with a particular AI model may be completely different tomorrow with the next version. AI models are in an extremely fast development cycle.

You’ve set up your automations perfectly, everything’s running? Then the next AI model update comes along and turns everything upside down. That’s the opposite of what a Smart Home should be – stable, reliable, low-maintenance.

In the video I explain why this constant change turns your Smart Home into a perpetual work-in-progress!

Reason 6: Computing Power – Local or Cloud?

If you want to run AI locally (which would actually be the only Home Assistant-compatible option), you need massive computing power.

Most of us run Home Assistant on a Raspberry Pi or similarly lightweight hardware. That’s enough for hundreds of automations – but not for compute-intensive AI models.

So back to the cloud? Then we’re back at Reason 1: cloud dependency. A vicious cycle!

Watch the video to see what hardware you’d really need for local AI – the numbers are sobering!

Reason 8: Privacy – Your Private Life

Yes, Reason 7 is missing from the transcript – probably a small mistake during recording! But Reason 8 is all the more important: Privacy!

Smart Home data is extremely private:

Camera images show your home and your family
Presence data reveals when you’re home and when you’re not
Sensor data shows your habits in the finest detail

Should this intimate information really end up in a cloud AI? Absolutely not!

In the video I explain why Smart Home data in particular is so sensitive and why you should be very careful about who you trust with this data.

Reason 9: Home Assistant Already Has Everything

Let’s be honest: Look at the list of integrations! Over 3,000 integrations, countless sensors, helpers, template functions – Home Assistant can already do just about everything.

What You Really Need

You can derive precise decisions from your sensors:

Motion sensors tell you if someone is home
Bluetooth beacons track your devices
Temperature sensors control the heating
Brightness sensors regulate the lighting

All of this deterministic, reliable, and with the precision you define in your automations.

In the video I show you that the real use cases for AI in Home Assistant can be counted on one hand!

Reason 10: AI Solves Problems You Can Solve Differently

The last reason is perhaps the most important: Do you really need AI for these problems?

Example 1: Presence Detection

Do you need AI to detect if someone is home? No!

Motion sensors in every room
Bluetooth beacons from smartphone or watch
Door sensors

All of this gives you deterministic, reliable presence detection – completely without AI!

Example 2: Heating Control

Do you need AI-powered heating control to squeeze out the last percent of optimization? Or would a simple day and night temperature be completely sufficient?

The answer is almost always: The simple solution is enough! In the video I give you more examples where AI seems complicated but the solution is actually simple.

But: AI Can Still Help!

After all the critical points, I promised: There are actually sensible use cases for AI in Home Assistant! Just not where most people expect them.

Use Case 1: Analyzing Log Files

Who doesn’t know this? Home Assistant floods you with log files, and you desperately ask yourself: “What’s actually going wrong here?”

AI models or language models are perfect for processing large amounts of text.

Simply copy the log files into ChatGPT or another language model and ask: “What’s the problem here?” Even if a direct solution doesn’t always come out, you at least get ideas for further research.

In the video I show you how this works in practice and which prompts work well!

Use Case 2: Debugging Jinja Templates

You’ve gotten tangled up in Jinja templates again and are completely at a loss as to why it’s not working?

Copy the template snippet into an AI and let it analyze it. The chances are good that you’ll get valuable tips on where the error lies.

This is, by the way, one of my personal main use cases for AI: understanding and debugging complex template syntax!

Use Case 3: Object Detection

The third sensible use case: Object detection in camera images.

“Is that the mail carrier at the door or the neighbor?” – this is actually a legitimate use case for AI (or more precisely: for machine learning).

Important distinction: Here we’re talking less about language models, but rather classical machine learning for image recognition. In the video I explain the difference and why it actually makes sense here.

Conclusion: AI Doesn’t Replace Logic

After all these arguments, the conclusion can be stated very clearly:

AI doesn’t replace logic in Home Assistant. At best, it can help build it better.

Home Assistant thrives on:

Deterministic rules
Local control
Privacy
Reliability

And these are exactly the values you should not sacrifice for the AI buzzword. Use AI where it truly adds value – in debugging, in development, in specific recognition tasks. But build your Smart Home on solid, transparent automations.

Make sure to watch the complete video – I go even deeper into each argument and show you practical examples!

What’s your take on AI in your Smart Home?

Write in the comments:

Are you already using AI features in Home Assistant?
Did I convince you, or do you see other sensible use cases?
Where would you like AI support?

Home Assistant A-Z: J is for Blinds

Sun, 23 Nov 2025 00:00:00 +0000

Welcome to the A-Z Series: J is for Blinds

In today’s episode of the Home Assistant A-Z Series we tackle a topic with far more potential than most people realize: blinds and roller shutters! From elegant dashboard control and time-based automations to fully automatic, sun-dependent shading – I’ll show you how to make your home more energy-efficient and comfortable.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

More Than Just Up and Down

Most people use their smart roller shutters only for the basics. But there’s so much more potential hiding in them! In this article and the accompanying video I’ll walk you through:

Dashboard control with live feedback
Time-based and event-driven automations
Groups and template sensors for a quick overview
Fully automatic, sun-dependent shading
Seasonal adjustments to your setup

Dashboard Control: The Foundation

The first step toward smart roller shutters is intuitive control through your dashboard.

Position Control with Live Feedback

If your roller shutters can report their position back, you can see in Home Assistant not just the current status, but also:

Move to precise intermediate positions using a slider
Watch live as the shutter reaches the desired position
Use classic Open/Close/Stop controls on a secondary level

In the video you’ll see how elegant this looks in practice!

Visualization on Floor Plans

Things get especially clear when you project your roller shutters onto a floor plan of your home. At a glance you can see:

Which shutters are open
Which are currently closing
The status of all windows at the same time

Under the hood: A simple picture-elements card with positioned shutter controls. I show you exactly how this works in the video!

Time-Based Automations: The Smart Home Classic

Constantly tapping buttons isn’t smart – so let’s automate!

Automation 1: Close Automatically at Night

The first useful automation makes sure roller shutters are closed at night. You can use various triggers:

State-based: When you go to bed (Smart Home state “Night”)
Time-based: At a specific time (different for weekdays and weekends)
Condition-driven: Only when it’s cool outside (to make use of the insulating effect)

In the video I show you concrete examples from my own setup!

Automation 2: Open Automatically in the Morning

Symmetrically, when you get up in the morning the shutters open again automatically. Alternatively, you can use the sun’s position as a trigger.

Intelligent Schedules with Helpers

For different schedules (weekday vs. weekend) schedule helpers are perfect. You can define them as “quiet hours” and reference them in your automations.

Groups and Overview: Everything Under Control

Grouping Roller Shutters

You can create any groups of roller shutters you like – for example:

All shutters in the living room
All shutters on the south-facing side
All shutters in the entire house

With a single click you can then open or close all shutters in that group.

Template Sensor for an Overview

A small template sensor shows you on your dashboard how many roller shutters are currently closed:

1
2
3
4
5
6
7
8
9


sensor:
 - platform: template
 sensors:
 closed_covers_count:
 friendly_name: "Closed Roller Shutters"
 value_template: >
 {{ states.cover
 | selectattr('state', 'eq', 'closed')
 | list | count }}

This way you always have a clear overview! In the video you can see how I use this on my dashboard.

Automatic Shading: The Game Changer

Now things get really interesting: fully automatic, sun-dependent shading!

The Two Components

My system consists of two automation groups:

1. Sun Position Calculation per Facade

The first group calculates for each cardinal direction whether the sun is currently shining on that facade:

Blueprint-based: I use a blueprint that I’ve instantiated four times
One helper per facade: North, South, East, West
Dynamic calculation: Takes the current sun position into account

I cover the technical details and the blueprint thoroughly in the video!

2. Individual Control per Window

The second group controls each individual roller shutter:

One blueprint per shutter: Each shutter can be configured individually
Window contacts taken into account: Window open? Shutter stays up!
References the sun-position helpers: Only closes when the sun shines on that facade

Example from my setup: The roller shutter in the utility room on the north side closes as soon as the sun (even in summer, only at the edges of the day) shines on that facade.

Why One Automation per Window?

This approach enables maximum flexibility:

Each shutter can be individually enabled or disabled
Different rooms can be controlled differently
Seasonal adjustments are easy to make

Seasonal Configuration: Adapting Throughout the Year

The great thing about this system: you can adjust which rooms should be shaded as the seasons change.

My Scenarios

Winter (currently):

✅ All shading automations disabled
🌞 I enjoy every ray of sunshine that enters the apartment

Transition periods (spring/autumn):

✅ Only bedroom automations enabled
🏠 Rest of the apartment: sunshine welcome
😴 Bedroom: should stay cool

Midsummer:

✅ All shading automations enabled
❄️ Maximum cooling through consistent shading

On my dashboard I have an elegant overview where I can see at a glance which automations are active. I show you this view live in the video!

Hardware Basics

Wondering how to make your roller shutters smart in the first place?

In my Shelly roller shutter video I cover in detail:

Hardware selection (Shelly Plus 2PM, Shelly 2 Gen3 Or at OBI: Shelly 2 Gen3, Shelly 2 Gen4 Or at OBI: Shelly 2 Gen4*)
Wiring in the flush-mount box
Software setup and security
Home Assistant integration

👉 To the Shelly Blinds Video

The Blueprints in Detail

The blueprints for sun-position calculation and individual control are the core of my system.

Interested in the details? Let me know in the comments under the video! If there’s enough interest, I’ll make a bonus video dedicated to these blueprints, covering:

Complete code
Step-by-step explanation
Customization options
Download links

Practical Benefits in Everyday Life

What does this actually get you?

Comfort

Automatic adjustment to sunlight
Never need to manually intervene again
Smart Home thinks ahead – even when you’re not home

Energy Efficiency

Cooler rooms in summer through consistent shading
Warmer rooms in winter through the insulating effect at night
Less air conditioning/heating required

Security

Presence simulation while on vacation
Automatic closing during storms possible
Integration with alarm systems

Level 1 – Basics:

Add roller shutters to Home Assistant
Set up dashboard control
Create first time-based automations

Level 2 – Comfort: 4. Create groups 5. Add template sensors for overview 6. Visualize on floor plan

Level 3 – Pro: 7. Implement sun-position calculation 8. Set up individual shading automations 9. Configure seasonal adjustments

I walk you through every step in detail in the video!

Further Links

More helpful articles from the A-Z Series:

Hardware:

Shelly Blind Control

The Home Assistant A-Z Series brings you the most important Home Assistant concepts in short videos and in-depth articles. A new letter every Sunday, a little more knowledge each time!

Home Assistant A-Z: H is for Helpers – Secret Heroes

Sun, 12 Oct 2025 00:00:00 +0200

Do you ever forget to take out the trash? Or have your automations grown so complex that even you can no longer keep track? Home Assistant helpers are the solution! These unassuming features can revolutionize your smart home life.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

What exactly are helpers?

Helpers are virtual entities in Home Assistant that act as “memory” or temporary storage for your automations. They can store states, perform calculations, or simply serve as digital sticky notes.

The brilliant part: Helpers exist only inside Home Assistant — they are not physical devices. Yet they behave just like real entities and can be used in all automations, dashboards, and scenes.

The most important helper types:

Toggle (Input Boolean): On/Off states
Number (Input Number): Values between a minimum and maximum
Text (Input Text): Store arbitrary text
Select (Input Select): Predefined options
Date/Time (Input Datetime): Remember specific points in time

Why helpers improve your smart home

Problem 1: Forgotten tasks

Sound familiar? Push notifications are swiped away in a second — and then forgotten. The video shows a clever solution: An automation reminds you the evening before to put out the trash bin. But instead of just sending a push notification, it also turns on a helper.

The helper appears as a tile on the dashboard — and stays there until you’ve completed the task and turn it off again. No more forgetting!

Problem 2: Complex automations

The more complex your automations become, the harder troubleshooting gets. The video shows a real-world example: A shading automation split into two parts:

One automation calculates whether the sun is shining on a particular side of the house
A second automation uses that result to control the blinds

The advantage: When something goes wrong, you can immediately see in the helper whether the sun calculation is working correctly. Complex logic is broken down into digestible pieces.

Problem 3: State management

The most powerful example in the video: A helper that manages the entire home status. With just four states (Home, Away, Vacation, Night), dozens of automations are controlled:

Light automations distinguish between day and night
Security features activate when nobody is home
Energy-saving functions kick in during vacation mode
Warnings trigger for open windows when leaving the house

One central helper replaces complex conditions in every single automation.

Practical helper ideas for your smart home

Digital reminders

Watering plants: Weekly reminder with dashboard display
Maintenance tasks: Filter changes, battery checks, etc.
Appointments: Trash collection, cleaning service, tradespeople

Storing intermediate values

Average temperatures: Combine multiple sensors into one value
Energy calculations: Break complex formulas into steps
Presence detection: Combine various sensors into one result

Complex states

Weather modes: Sunny, rainy, windy — for different automations
Activity modes: Working, relaxing, sleeping, party
Security levels: Normal, heightened, vacation, maintenance

Using helpers correctly — what the video shows

The video walks you through step by step:

Where to find helpers — Navigating to the settings
How to configure helpers — Practical examples
Integration into automations — Concrete usage
Dashboard display — User-friendly presentation
Troubleshooting — How to spot problems

Especially valuable: the live demonstration

Explaining helpers in writing is one thing — seeing them in action is another. The video impressively demonstrates:

How the dashboard changes when a helper is activated
The connection between automations and helpers
Practical clicks through the user interface
Real use cases from a working smart home

Avoiding common beginner mistakes

Too many helpers at once

Mistake: Creating dozens of helpers for every possible scenario right away. Better: Start with one or two simple helpers and build experience from there.

Confusing names

Mistake: Naming helpers something like “Boolean1” or “Input_xyz”. Better: Use descriptive names like “Trash_Yellow” or “House_Status”.

No documentation

Mistake: Coming back months later with no idea what a helper was for. Better: Write descriptions into the helper configuration.

Why you should definitely watch the video

Helpers are a game changer for Home Assistant — but their full potential only reveals itself once you understand and use them correctly. The video shows three completely different use cases that illustrate just how versatile these seemingly simple tools are.

You’ll learn concretely:

How to work with the helpers interface in practice
How helpers can improve your existing automations
Pro tips for complex state management
Why one well-designed helper can replace dozens of complicated conditions

Three complexity levels in the video

Beginners: The trash reminder is a perfect entry point
Intermediate: The shading logic shows helpers as automation building blocks
Advanced: The home status management demonstrates enterprise-level smart home architecture

No matter what level you’re at — you’re guaranteed to find new ideas for your smart home!

The difference from other smart home systems

While commercial smart home hubs often impose rigid structures, Home Assistant helpers give you the freedom to design your system around your own needs.

The video shows this impressively: With just a few clicks you can create tailor-made solutions that simply wouldn’t be possible in other systems. This flexibility is what makes Home Assistant so powerful — and helpers are a big part of that.

Conclusion: Small helpers, big impact

Helpers are the secret heroes of your smart home installation. They work invisibly in the background, simplify complex automations, and make your system more maintainable and understandable.

The video perfectly demonstrates their versatility — from simple reminders to complex state management. After watching, you’ll see your smart home with fresh eyes and will surely discover your own use cases for helpers.

What’s your favorite helper? Write it in the comments! And if you’re enjoying this A-Z series, check out the other episodes — each one brings you one step closer to becoming a smart home pro.

Home Assistant AI Automations: How Dangerous Are They?

Sun, 24 Aug 2025 00:00:00 +0200

It felt like an early Christmas gift: Home Assistant 2025.8 finally promises real AI support for your automations. Imagine being able to press a button and have artificial intelligence suggest perfect names for all your automations. Sounds like a dream, right?

But sometimes the most beautiful dreams turn into nightmares. What looks like a breakthrough at first glance can turn your carefully built smart home into a chaotic naming mess — and the tricky part is you won’t notice until it’s too late.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

When Progress Becomes Regression

The Tempting Promise of the AI Suggest Feature

You probably know the feeling: you’ve just built a brilliant new automation and you’re staring at the infamous name field. “Automation 47” would be honest, but not particularly helpful. That’s where the new “Suggest” feature in Home Assistant 2025.8 seems to come to the rescue. One click, and the AI proposes a name. Magic? Almost.

What happens in the background is genuinely impressive: Home Assistant doesn’t just send the YAML code of your current automation to the AI model — it also sends the names of all your existing automations. In theory, the AI has everything it needs to align with your existing naming scheme.

But this is where the trouble begins. In the video, I show exactly what happens when the AI encounters a typical “organically grown” smart home — and why the result is often disastrous.

The Great Naming Dilemma

Imagine spending weeks desperately searching for a specific automation in your list of hundreds. Was it “Blinds down”, “Close shutters”, or “Rolladen automatisch”? Or maybe “Jalousie runter”?

The truth is: most of us haven’t been consistent when naming our automations. Sometimes German, sometimes English, sometimes verbose, sometimes terse. The AI can only work with what you give it — and if your existing names are a hodgepodge, it will only amplify that chaos.

Why This Seemingly Harmless Feature Can Ruin Your Smart Home

The insidious thing about the new Suggest feature isn’t what it does — it’s what it can’t do. It can’t read your mind. While you might have a sophisticated naming scheme in your head (“Room_Device_Action” or similar), that knowledge is invisible to the AI.

The result? A gradual decay of your automation structure. Today the AI suggests “Living room light on”, tomorrow “Activate kitchen lighting”, and the day after “Turn on bedroom lights”. Within a few weeks you have a Babylonian language muddle that makes your smart home practically unusable.

In the video, I demonstrate this using a real installation with over 100 automations — the result is both alarming and instructive.

The Solution: How to Use AI the Right Way

The Game-Changer: Batch Processing Instead of One-at-a-Time

But there is hope! The problem isn’t AI itself — it’s the way it’s being used. What if you didn’t have to process each automation individually, but could make your entire installation consistent in one go?

That’s exactly what I show in the video. The trick is simple yet incredibly effective: instead of letting the AI work on automations one by one, you hand it all your automations at once — together with precise instructions about what the perfect naming scheme should look like.

The Secret Is in the Details

What the Home Assistant feature can’t do, you do manually: you give the AI a crystal-clear assignment. Not “do something sensible”, but “use exclusively German terms, apply the scheme Room_Device_Action, and follow these examples”.

In the video you can see how I implement exactly that — from extracting automations.yaml to feeding the perfectly renamed automations back in. The process is simpler than you think, but the impact is dramatic.

Why Reasoning-Capable AI Models Make the Difference

Things get particularly interesting with large installations. While basic AI models quickly lose the overview, reasoning-capable models like GPT-5 Thinking can identify relationships and develop consistent patterns.

The video shows impressively how the AI doesn’t just assign names — it develops a well-thought-out system. Similar automations are grouped recognizably, edge cases are handled intelligently, and in the end you have an installation that looks as if a professional had planned it from the start.

The Step-by-Step Path to Perfection

The video walks you through the complete process — and I promise it’s simpler than you think:

Step 1: Take Stock

First, download your automations.yaml from your Home Assistant installation. This file contains all your automations in YAML format — essentially the blueprint of your smart home.

Step 2: Choose the Right AI

Not every AI is suited for this task. In the video I explain why I use GPT-5 Thinking and why reasoning-capable models deliver significantly better results for complex naming tasks.

Step 3: The Perfect Prompt

This is where the real difference is made. I show you my tested prompt that turns chaotic automation names into a perfectly structured list. You can watch the AI work and make decisions in real time. The prompt is available to copy in the video description on YouTube — just click into the video above.

Step 4: Patience

While the AI is working, it’s a great time to follow the channel — especially if AI in the context of smart home interests you. This may be my first video on the topic, but it certainly won’t be the last.

Step 5: The Result

The outcome is impressive. What was a jumble of different naming styles becomes a clean, coherent structure. Every automation has its perfect place, similar functions are instantly recognizable, and navigation becomes effortless.

Step 6: Feed It Back

The final step is importing the result back into Home Assistant. A quick restart via the Developer Tools, and your installation shines in a whole new light.

The Outcome: From Chaos to Order

What you see in the video is more than a technical demonstration. It’s the transformation of an organically grown, chaotic installation into a professionally structured smart home.

The before-and-after views speak for themselves: where “Automation 17”, “Kitchen lights on”, “Licht Wohnzimmer”, and “Beleuchtung_Schlafzimmer_automatisch” once sat side by side, you now find a crystal-clear structure.

The Long-Term Benefits

After the transformation you get:

Lightning-fast navigation — you find every automation instantly
Easy maintenance — similar automations are logically grouped together
Professional appearance — the system becomes understandable for other family members too
Future-proofing — new automations automatically follow the established scheme

The Ultimate Flexibility Bonus

The best part of this approach is what I show at the end of the video: total flexibility. Not happy with the new scheme after a few weeks? No problem — just adjust the prompt and run the process again.

No more manually renaming hundreds of automations. No more hours of clicking. Simply change the prompt, let the AI work, done. This flexibility is the real game-changer.

What to Expect in the Video

The video is a complete hands-on guide with no boring theory. You’ll see:

Live demonstration of the problematic Suggest feature
Step-by-step guide for the better approach
Real before-and-after comparisons from a 100+ automation installation
The exact prompt I use
Tips on choosing the right AI model for best results
Pitfalls and how to avoid them

This isn’t theoretical — it’s pure practice. You can start immediately and apply the method to your own installation.

Why You Should Watch the Video

This article gives you a solid overview, but the video shows you the magic in action. Watching a chaotic mess of automation names transform into a perfectly structured list is simply fascinating.

You’ll also get insights in the video that are hard to convey in writing:

How the AI “thinks” and makes decisions
Which naming patterns work particularly well
How to handle edge cases and exceptions
Why some AI models deliver better results than others

Conclusion: The Difference Between Using AI and Using AI Correctly

The new Suggest feature in Home Assistant 2025.8 is a bold first step toward AI integration. But as is often the case with new technology: the first attempt is rarely the best.

The video doesn’t just point out the weaknesses of the current implementation — it gives you a concrete, immediately actionable alternative. One that not only works better, but is also more flexible and future-proof.

The takeaway? AI is a powerful tool — but only if you know how to use it correctly. The Home Assistant Suggest feature is like using a hammer as a scalpel. It sort of works, but the result is rarely satisfying.

With the approach from the video, you have a precision instrument instead. A tool that makes your smart home not just nicer, but more professional and maintainable.

Watch the video, try it yourself, and let the results surprise you. Your automations — and your future self — will thank you.

Have you had any experiences with the new AI feature? And what other use cases for AI in Home Assistant do you see? Feel free to leave a comment — I’m curious to hear your ideas!

Home Assistant A-Z: B is for Blueprints

Sun, 27 Jul 2025 00:00:00 +0200

Imagine being able to install complex automations with a single click — pre-configured, tested, and ready to go. Sounds too good to be true? That’s exactly the idea behind Home Assistant Blueprints!

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

What are Blueprints, exactly?

Blueprints are pre-built automation templates for Home Assistant. Imagine someone has already created the perfect automation — for motion sensors, notifications, or complex lighting controls — and you can simply adopt it.

The concept is brilliantly simple: a Blueprint defines the logic of an automation, but leaves the specific devices and settings up to you. You import the Blueprint, select your own sensors and switches, and the automation is up and running.

For example: a Blueprint for “light on motion” works with any motion sensor and any light — you just pick your specific devices. The entire logic is already programmed and tested.

Why does this matter for your smart home?

Let’s be honest: building automations from scratch can get complicated. Especially for advanced scenarios like “dim lights based on time of day and presence” or “send a notification only under certain conditions.” With Blueprints, you skip all that development work.

In practice, this means: instead of tinkering for hours, you install a Blueprint in 2 minutes. The automation runs immediately and has already been tested by other users in real-world setups.

How does it work in Home Assistant?

Let’s take a concrete look. To use a Blueprint, go to Settings → Automations & Scenes, then Blueprints, and click “Import Blueprint.”

You can find Blueprints in several ways: in the official Home Assistant Community (linked directly in the import dialog), on GitHub, or in other forums. Just copy the Blueprint URL and paste it into Home Assistant.

After importing, the Blueprint appears in your list of available Blueprints and you can use it right away. Important: you can use a single Blueprint multiple times — for example, with different configurations. You might use the same motion-light Blueprint for the hallway and for the bathroom. You create two separate automations, both using the same Blueprint, but with different sensors and lights.

The most common pitfalls

A frequent mistake is trusting a Blueprint blindly without understanding it. Sure, it’s quick — but even if you’re saving time by not building the automation from scratch, you should still take a moment to understand what the Blueprint does. Without understanding its structure, you’ll be stuck if something stops working. And strictly speaking, a poorly written Blueprint could even execute things in your home that you never intended.

The second pitfall: using outdated or poorly documented Blueprints. Not every Blueprint on the internet is well-maintained. Some only work with older versions of Home Assistant; others have hidden bugs. Always check the ratings, comments, and the last update date. Blueprints from the official Home Assistant Community are generally the safest choice.

One last common mistake: installing too many Blueprints at once without properly testing them. Each Blueprint creates new automations in your system. If multiple Blueprints have similar functionality — for example, different lighting controls — they can interfere with each other. Install one Blueprint at a time and test thoroughly before moving on. It will save your nerves and prevent frustration.

What can you do with Blueprints creatively or practically?

Blueprints open up an enormous world of possibilities without requiring you to program sophisticated logic yourself. But it also works the other way around: you can create your own Blueprints to standardize similar automations. If you have a lighting automation for multiple rooms, there’s a good chance they all work largely the same way. Why not turn it into a Blueprint and simply configure the sensors and lights per room? That saves you effort in the long run when maintaining your automations.

Which Blueprint would you start with? Share your idea in the comments below.

Next up is “C” for Cloud Integrations, or check out the overview of all A-Z posts.

Home Assistant A-Z: A is for Automations

Sun, 20 Jul 2025 00:00:00 +0200

Every day you flip a light switch at least 50 times. What if your home could take care of that for you — and save energy, improve your security, and give you back 15 minutes every single day?

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

What is this actually about?

Automations are the heart of your smart home. They handle tasks for you — automatically, of course.

The concept: If something happens, then do something.

When it gets dark outside, turn on the outdoor lighting
When nobody is home, arm the alarm system

You need a trigger (e.g., sunset), can narrow things down with conditions (e.g., only when nobody is home), and define one or more actions (e.g., turn on the lights).

Why does this matter for your smart home?

Let’s be honest: you can control your lights via an app. But imagine coming home exhausted, arms full of grocery bags — and the lights just turn on automatically. Or you forget the stove again — an automation shuts it off after 30 minutes.

Benefits:

Time savings: No opening apps, no searching for switches, no forgotten devices
Security: Automatic shutoffs, notifications, and presence simulations
Convenience: Your home thinks ahead and takes care of routine tasks for you

My three most important automations easily save me 15 minutes a day!

How does this work in Home Assistant?

Let’s look at an example:

Trigger: Wind sensor reports gusts above 30 km/h
Action: Automatically retract the awning

Here’s how:

Go to Settings → Automations & Scenes
Click Create Automation
Select Start with an empty automation
Define triggers, conditions, and actions
Name and save the automation

The most common pitfalls

1. Not accounting for all real-life situations The awning retracts when it’s windy — but what happens when you manually extend it again afterwards? The automation won’t fire because it only triggers when wind speed crosses the threshold. Solution: Add additional triggers or conditions to handle edge cases.

2. Problems with multiple triggers If you use multiple triggers (e.g., “Wind gusts OR awning is extended”), the automation can fire even when you intentionally extend the awning yourself. Solution: When using multiple triggers, always use conditions to verify that the actual condition is still met.

3. Wrong automation mode The default mode “Single” means: if the automation is triggered again while it’s still running, nothing happens. This can be problematic for longer-running automations. Solution: Choose the right mode (Single, Restart, Parallel, Queue) depending on your use case. Learn more in this article.

What creative or useful things can you do with this?

With automations, the possibilities are almost endless. For real value, start with automations that eliminate repetitive manual tasks.

My favorite: “Good Morning” automation

Open the roller shutters
Set the lights in the bathroom and kitchen
Start music depending on the day of the week

So many things I’d otherwise have to do by hand every single day!

Conclusion

Automations make the difference between a connected home and a truly smart home. They save time, improve security, and simply make life more comfortable.

My tip: Start small, test thoroughly, and expand your automations step by step. You’ll soon wonder how you ever lived without them!

Which automation saves you the most time? Share your idea in the comments below. Continue with “B” is for Blueprints or check out the overview of all A-Z articles.

Make Your Washing Machine Smart? 5 Things to Know

Sun, 29 Jun 2025 00:00:00 +0200

The first video about the dishwasher got more reactions than expected. Not because of the technology – but because many people had similar problems that I hadn’t even addressed: plugs that melted. Devices that behaved strangely after being switched off. Questions about Aquastop and solar surplus.

The five points here came directly from that feedback.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

1. Watch the Maximum Load

Perhaps the most important point first: many smart plugs are only rated for 10A/2500W. Some appliances – especially older models – can draw 2800 or even 3000 watts during the heating phase. In the worst case, this can cause the plug to overheat or even melt – as happened to one viewer. Measure your device’s power draw beforehand, or check the rating plate. Better to use a plug rated for 16A/3500W, e.g. Shelly Plug (not the S), Sonoff, TP-Link, or AVM.

Suitable smart energy-monitoring plugs (affiliate links):

Fritz!DECT 200 https://amzn.to/44armtk
Shelly Plug S https://amzn.to/4k0PZie – or at OBI: https://www.awin1.com/cread.php?awinmid=9326&awinaffid=2527487&ued=https%3A%2F%2Fwww.obi.de%2Fp%2F7119407%2Fshelly-smart-stecker-plug-s-gen3-weiss
TP-Link Tapo https://amzn.to/4lewLq3
More options: https://amzn.to/4lcpZRE

2. Cutting Power – Is That Even Safe?

A valid concern raised by the community: what about Aquastop and leak protection? In most cases, switching off after the wash cycle is actually safer, because the valve is closed when unpowered. However, some manufacturers have systems that require a constant power supply. When in doubt, check the manual or contact the manufacturer. For most appliances, switching off after the cycle is harmless – and saves standby power.

3. What Does “Smart” Actually Mean?

It’s not just about detecting the “done” status – with solar surplus or a dynamic electricity tariff you can get even more out of it. A basic setup with power monitoring is the foundation for further automations. If you have solar panels or use a dynamic tariff, you can switch the plug on at the right time – a few lines of automation in Home Assistant are all it takes.

4. Door Sensor, TTS, Angry Mode: Next-Level Smart!

A community tip: combining a door sensor with text-to-speech announcements takes things to the next level. Automatic resets, funny phrases, and even increasingly “annoyed” reminders motivate everyone to unload the machine – kids included! One viewer even used ChatGPT to generate a set of messages that get progressively more irritated the longer the wait.

5. Switching On – How Does That Work?

Whether your dishwasher automatically resumes after a power interruption depends on the model – just try it out. Start the appliance, pull the plug, plug it back in – if it keeps running, you’re good to go. If not, you can still use the power monitoring; you just won’t be able to start it automatically via an automation. Personally, I switch the plug on with a long press on the light switch, for example.

Conclusion: With these tips your appliances become truly smart – and you get the most out of your household setup. Watch the video for all the details and practical examples!

5 Automation Mistakes Everyone Makes in Home Assistant

Sun, 22 Jun 2025 00:00:00 +0200

Sound familiar? You built an automation, but it doesn’t work the way you intended? Or you have lots of automations but keep running into problems? Then you’re in the right place! In this article I’ll show you the five most common mistakes when designing Home Assistant automations – and how to avoid them easily.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

1. Automations That Are Too Complex

If you no longer remember what your automation is actually supposed to do after two weeks, it has probably become too complex. Split large automations into several smaller ones – this makes them easier to understand and maintain. For example: control your blinds with multiple automations for different triggers rather than cramming everything into one.

2. Too Many Automations Interfering With Each Other

More isn’t always better! When multiple automations access the same entity, conflicts can arise. Think carefully about when it makes sense to keep automations separate – and when it’s better to combine them to avoid race conditions.

3. Not Tested – or Only Tested in Daily Use

Test your automations deliberately before letting them run in everyday life. Think through which triggers, conditions, and actions you need in advance – and verify that everything works as intended. It saves frustration for you and your family!

4. Unclear Naming

Give your automations and entities clear, unambiguous names. It’s worth keeping a small glossary so you always know what’s meant – and can find automations quickly when you need them.

5. Wrong Automation Mode

Many problems arise because the wrong mode (Single, Restart, Parallel, Queue) was chosen. Learn how the modes work – and pick the right one for your automation. More on this in the video!

Summary: With a few simple tricks, your automations become more reliable and easier to manage. If you want even more tips, check out the video!

5 More Automation Mistakes in Home Assistant – Are You Affected? – The follow-up: new pitfalls around trigger IDs, hardcoded time values, and AI-generated automations
Securing Home Assistant – 5 Mistakes to Avoid in Your Smart Home – Once your automations work, the security mistakes come next: the next level

Home Assistant Automation Modes Explained for Beginners

Sun, 15 Jun 2025 09:00:00 +0200

Home Assistant Automation Modes for Beginners

You built an automation but it sometimes behaves strangely? Or you’re wondering what the different modes like Single, Restart, Parallel, and Queue actually mean? In this article I’ll explain the differences, show you practical examples, and help you find the right mode for your automations.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

What Are Automation Modes?

In Home Assistant, you can configure for each automation how it behaves when it is triggered multiple times. This is important so your automations work reliably and as intended.

Single: The automation runs only once. If it is triggered again while still running, nothing happens.
Restart: If the automation is triggered again, the current run is cancelled and it starts over from the beginning.
Parallel: The automation can run multiple times simultaneously.
Queue: New triggers are placed in a queue and processed one after another.

Practical Examples

Take a look at the video for examples like motion-triggered lights, doorbells, or voice announcements. There is a right mode for every use case. You should use Parallel with caution though — find out why in the video.

Conclusion: With the right mode your automations become more reliable and you save yourself a lot of frustration. Watch the video to see all the details and examples!

Make Any Dishwasher Smart – No Cloud, No Rewiring

Sun, 25 May 2025 00:00:00 +0000

Your dishwasher isn’t smart yet? Not for long! In this article I’ll show you how to bring any old appliance up to speed with one simple trick – no rewiring, no cloud, just a small smart plug. The same principle works equally well with washing machines, dryers, or any other household appliance that runs a cycle and then gets forgotten.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

What you get out of it

Automatic notification when the cycle is done
Saved standby power
Increased safety at home
Ability to switch the appliance off remotely

The idea: energy monitoring instead of cloud

Many new appliances are “smart” – but usually only through manufacturer-dependent clouds. Why buy something new when the existing machine still works perfectly? With a smart plug like the Shelly Plug S (or any other relay with energy monitoring) you can retrofit any appliance and integrate it into Home Assistant – completely local, no cloud required.

The following devices are suitable for this project:

Shelly Plug S (affiliate link) Or at OBI: Shelly Plug S (affiliate link)
Shelly Plus 1 PM (affiliate link) Or at OBI: Shelly Plus 1 PM (affiliate link)
Sonoff POW R2 (affiliate link)
Sonoff POW Elite (affiliate link)
Smart Plug (affiliate link)

How the detection works

The idea is simple: the power consumption of the appliance is measured. If it exceeds a certain threshold for a certain period of time, the wash cycle is running. If it drops below that threshold – again for a defined period – the appliance has most likely finished. To prevent the automation from reacting to every small spike, a hysteresis is built in, meaning a delay or waiting period.

Determining typical values

Measure a complete cycle of your appliance and observe the power draw. In my case, that’s more than 5 watts for at least 5 minutes (appliance running) and less than 5 watts for at least 5 minutes (appliance done). The exact values can vary depending on the model – experiment and adjust the thresholds accordingly.

Implementation in Home Assistant

I also walk through this step by step in the video – feel free to check it out for the screencast!

Add the device: Integrate the Shelly Plug S or another smart relay with energy monitoring into Home Assistant.
Create sensors: Set up threshold sensors (e.g. using a template or a threshold sensor) that detect the appliance’s status.
Automation: Create an automation that notifies you when the appliance is done – or that cuts power to the device completely after the cycle finishes.

Robust template sensor: handling connection drops

A simple template sensor has one weak spot: if the smart plug briefly loses its connection (Wi-Fi dropout, Home Assistant restart), the power sensor returns unavailable – and the binary sensor snaps to false. That incorrectly triggers a “cycle done” notification even though the machine is still running.

The fix: freeze the last known state for as long as the plug is unreachable. In the video I only showed the basic version – viewer Andreas Schneider sent me a more robust configuration that I’m happy to share here:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19


binary_sensor:
 - name: "Dishwasher active"
 unique_id: dishwasher_active
 delay_off:
 minutes: 7
 delay_on:
 minutes: 2
 state: >-
 {% set switch = states('switch.dishwasher_plug') %}
 {% set power = states('sensor.dishwasher_plug_power') %}
 {% if switch == 'off' %}
 {{ false }}
 {% elif power in ['unavailable', 'unknown'] %}
 {{ this.state == 'on' }}
 {% else %}
 {{ power|float > 5 }}
 {% endif %}
 icon: "{{ 'mdi:dishwasher' if this.state == 'on' else 'mdi:dishwasher-off' }}"
 availability: "true"

Adjust the entity IDs (switch.dishwasher_plug, sensor.dishwasher_plug_power) to match your own setup. The threshold (> 5) can be tuned as described above.

Why this configuration is better:

delay_on: 2 min – prevents short startup spikes from activating the sensor too early
delay_off: 7 min – buffers brief pauses mid-cycle (e.g. during heating phases)
The elif block freezes the state on connection loss instead of falling to false
availability: "true" keeps the sensor itself always available, regardless of the plug’s state

Practical example: saving standby power

You can also see this workflow in the video as a screencast – check it out if you want to watch the implementation live!

After the wash cycle, I switch the dishwasher off completely. My appliance draws 4 watts in standby – that’s 35 kWh per year, or roughly €12 at €0.35 per kWh. You still need to subtract the smart relay’s own consumption of about 1 watt, which leaves around €9 in savings per year. That means the Shelly Plug S pays for itself in just over a year. Take a measurement on your own appliance – you might be surprised what a power drain it actually is.

Benefits & safety

No more standby, no voltage at the appliance
Greater safety (e.g. when away from home for longer periods)
Control and monitoring from anywhere

Conclusion

With a simple smart plug and Home Assistant you can make any old appliance smart – no cloud, no rewiring, and no vendor lock-in. You save electricity, improve safety, and always know whether your dishwasher (or any other appliance) has finished its cycle.

→ This video generated a lot of feedback. I’ve compiled the most useful practical tips from the community in a follow-up article: Making your washing machine & dishwasher smart? 5 things you should know!

Never Forget to Put the Bins Out Again with Home Assistant

Tue, 01 Apr 2025 00:00:00 +0000

Do you keep forgetting to put your bins out in time? With two Home Assistant integrations — Waste Collection Schedule and Card-Mod — you’ll get a prominent alert sent straight to your smartphone and displayed on your dashboard. Once the job is done, you can confirm the alert so it disappears from the dashboard. I’ll show you how to get this working in three simple steps.

To load the video, please click the image. Please note that by doing so, data will be transmitted to YouTube.

The whole setup comes down to three simple steps:

Install HACS and the integrations: We install HACS and set up the required integrations.
Configure Waste Collection Schedule: I’ll show you how to automatically capture your bin collection dates.
Set up the dashboard alert: You’ll learn how to add a prominent warning to your dashboard and make it disappear once the bins are out.

At the end, I’ll share a bonus tip — a small hidden feature of the integration. Let’s get started!

Installing Everything

HACS

I’ll quickly walk through installing HACS in case you haven’t done it yet. If you’re already familiar with it, feel free to skip to the next section — it only takes a moment, because HACS is really quick to set up.

If you haven’t installed HACS yet, you’ll find all the details at hacs.xyz. If you want to get it done fast, just run this command on your system:

1

wget -O - https://get.hacs.xyz | bash -

Afterwards, restart Home Assistant and you can set up HACS via “Add Integration”. This requires authentication via GitHub. You’ll be guided through the process almost automatically. Once everything is done, you’ll see a new HACS entry in the Home Assistant sidebar on the right.

Waste Collection Schedule & Card-Mod

Now we need two integrations, both available through HACS:

Waste Collection Schedule (for parsing bin collection dates)
Card-Mod (for a visually prominent display on your dashboard)

Steps:

In Home Assistant, go to HACS in the sidebar.
Search for “card-mod” and “waste collection”.
Download both integrations by clicking the menu on the right and confirming “Download” twice.
A restart of Home Assistant may be required after installation.

Setting Up Waste Collection Schedule (WCS)

Waste Collection Schedule (WCS) supports a wide range of providers. If your provider isn’t listed but offers calendar files in ICAL format, you can easily add them via “Generic”.

In a spot check of various districts in Germany, I didn’t find a single one that wasn’t already in the list.

Setting up your provider in WCS:

Go to: Settings > Integrations > Add Integration and select “Waste Collection Schedule”.
Select your country, e.g. Germany.
Search for your source: Look up your city or district.

Adding the URL:

Copy the URL from your waste management provider’s website.
Paste it into the setup dialog under “URL”.

Creating Sensors

Give each sensor a descriptive name, for example “Green Bin”.
In the “Value Template Preset” field, select “Numeric Days To”.
At the bottom under “Types”: Choose the correct label, e.g. “Organic Waste”.

Automations & Dashboard

There are several ways to use this information through automations or dashboard visualizations. I’ll show you two options:

Option 1: Notification via Automation

Go to: Settings > Automations and create a new automation.
Give it a name, for example “Bin Reminders”.
Set the trigger: Click “Add Trigger” > “Time & Location” > “Time” > “Fixed Time”.
- Choose a time when you’d like to be notified, e.g. late afternoon the day before collection.
Define conditions: Add a “Choose” block to distinguish between different bin types.
- For example: if the state of the green bin sensor is “1” (meaning collection is scheduled for the next day), you want to be notified the afternoon before.
Set actions:
- Choose “Send Notification” and enter a message, e.g. “Put the green bin out”.
Add a separate option for each additional bin type and define the corresponding conditions and actions.

This automation ensures you reliably receive reminders whenever it’s time to put your bins out.

Option 2: Display on the Home Assistant Dashboard

I know the problem all too well: you get a notification, you register it, and then forget about it anyway. In the worst case, you accidentally swipe it away.

That’s why I’ve found it far more effective to display the reminder on the Home Assistant dashboard — in a way that only disappears once you actively confirm it.

You can easily extend the automation you just created to handle this.

Preparation: Create a Helper

Go to: Settings > Devices & Services > “Helpers” tab.
Create a new helper: Select “Toggle”.
Name the toggle something like “Put green bin out”.
This toggle will be used to display and manage the bin collection status on your dashboard.

Extending the Automation

Go back to the automation you created and open the configuration for “Option 1”.
Add an additional action:
- Alongside the notification, add another action:
- “Input Helper” > “Turn on” > select your helper “Put green bin out”.

Setting Up the Dashboard Display

Add a tile to your dashboard that displays the “Put green bin out” helper.
Configure visibility:
- Set a condition so that this tile is only shown when the helper is turned on.

Your automation will now activate the helper the day before collection and display it on your dashboard. Once you’ve put the bin out, you tap the tile, which sets the toggle back to “Off” — and the tile disappears.

The whole cycle repeats in one or two weeks, and you’re guaranteed never to forget to put your bins out on time again. Unless you’re on holiday and can’t see the dashboard from there.

Fun Fact

Thanks to the Waste Collection Schedule integration, you can also display your collection dates in Home Assistant’s calendar view. So if you ever want to see your entire bin collection schedule at a glance, that’s easily possible.

And that’s it! Your Home Assistant will now reliably remind you to put the bins out on time.