Home Assistant A-Z: O is for Offline – Does Your Smart Home Work Without 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.

Note: Links marked with affiliate link are affiliate links. As an Amazon Associate I earn from qualifying purchases. This means I receive a small commission if you purchase through these links — at no extra cost to you. The revenue helps me run this blog and YouTube channel and keep creating content. Thank you for your support!
― Joachim

Failsafe on Smart Home? Sure — But Secure!

Home Assistant A-Z: O is for Offline – Does Your Smart Home Work Without Internet?

A Confession at the Start of 2026

Why Offline Functionality Matters

Internet Outages Are Not Rare

The Smart Bed Example

A Real-World Example From My Smart Home

The Window Reminder Automation

The Problem With Cloud-Based Sensors

The Fix: Use Local Sensors

Resilient Automations With Fallback Values

Float Conversion With a Default Value

Safety Through Fallback Logic

Second Example: Variable Wait Time

The Resilient Solution

How Do You Identify Offline-Dependent Integrations?

In the video I show you:

Why I Turn Off the Fritzbox at Night

My reasons:

My Three Most Important Tips for You

1. Make Core Functions Work Offline

2. Comfort Functions Can Be Dependent

3. Review Your Automations for Resilience

Conclusion: Resilience Is Not Rocket Science