Cloud on Smart Home? Sure — But Secure!

3 Smart Home fails: devices I would NOT buy today!

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

Imagine: you get up in the morning, want to raise the blind – and nothing happens. Try the app? Nothing. Try the physical switch directly? Dead. And here’s the kicker: the fault is buried deep inside a wall-mounted junction box.

That was the moment I realised: my smart home had just turned into a nightmare. And I’m not alone with experiences like this.

Today I’m showing you three devices that made it very clear to me where smart home can really go wrong. Not theoretical problems – but real fails that cost me time, money and nerves. We’re talking about 14 actuators all failing. A robot vacuum that became useless overnight. And false alarms waking me up in the middle of the night.

Watch the video – I demonstrate the problems live and show you what you can learn from them.

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

Fail #1: Shelly 2.5 – When 14 actuators died at the same time

The slow death inside the wall

This is a Shelly 2.5 – an actuator for roller shutters and blinds. I have 14 of them installed. Fourteen! Nearly all in junction boxes, permanently wired behind wallpaper and plaster. My expectation was pretty clear: install once, close up, forget it. Set and forget.

On the software side I was happy for a long time: locally controllable, great Home Assistant integration, no cloud dependency. Exactly what you want.

And then the drama began.

The same defect – 14 times

In all – yes, literally all – of these Shelly 2.5 actuators, one component failed after some time, one by one. All fourteen, always the same defect. Morning routine, raise the blind? Nothing. App? Nothing. Physical switch? Dead.

Now here’s the real nightmare: these things are of course sitting in junction boxes. That means: open the wall, pull out the actuator, desolder the capacitor, solder in a new one, reinstall, close the wall. Per actuator. Fourteen times.

That was a genuine maintenance disaster for me. And I’m not alone. There are masses of reports about this Shelly generation online.

In the video I show you exactly what went wrong and how I carried out the repair. The detailed repair guide is in this separate article.

Small consolation: repair is possible

With a soldering iron you can swap the faulty component for a few cents in parts. But honestly: do you really want to open 14 wall boxes and replace capacitors?

Important note: this problem affects specifically the Shelly 2.5. The successors Shelly Plus 2PM and the Gen 3 and Gen 4 are ones I use heavily myself and have had zero failures with so far. So this isn’t about bashing the manufacturer across the board.

The key lesson

Wait for long-term community experience before buying new products. First generation? Let others be the testers. Second generation with solid reviews over a year? Then go ahead.

Fail #2: Shark robot vacuum – When the cloud kills your integration

From smart home star to useless appliance

The second device frustrated me in a completely different way. It’s about my Shark robot vacuum. And upfront: the hardware is perfectly fine. It vacuums well, navigates decently, does its job.

For months I had it deeply integrated into my smart home. Built automations along the lines of: “When nobody’s home, start cleaning.” The Home Assistant integration ran perfectly. This wasn’t a toy – it was a solid, reliable part of my daily routine.

Watch in the video how well the system worked – before everything fell apart.

One app update. One dead integration.

And then, one morning: automation triggers – nothing happens. Home Assistant shows: connection lost. Maybe a bug? Open the app – it works. Robot starts via app. But the Home Assistant integration? Dead. Still dead weeks later. Permanently.

What happened? The Shark app had updated itself automatically – as apps do. Completely normal, in the background. Without me actively deciding anything or consciously triggering it.

But with this update, something had changed in the cloud interface. The result: the Home Assistant integration was broken. No workaround, no fallback, no local API.

The moment of realisation

That was the moment I understood: I didn’t buy a device I’m in control of. I bought a device whose capabilities can change at any time via a server update. Without my consent. Without warning. And I can do nothing about it.

In the video I explain in depth why this is a fundamental problem with many cloud-dependent devices.

Imagine buying a car – and a year later the manufacturer says: “Sorry, the radio only works with our app now.” That’s exactly what happened here. Except that the “radio” in my case was the entire smart home integration.

The lesson: an exit strategy is mandatory

Cloud is convenient – but you always need an exit strategy.

Is there a local API?
Can I flash alternative firmware?
Does the device work without internet?

Bose recently handed us a similar case. If that interests you, here’s the article about Bose SoundTouch.

Fail #3: Sonoff Zigbee motion sensor – The night-time false alarms

Bought cheap, paid dearly

The third device looks harmless at first glance: a Sonoff Zigbee motion sensor. Cheap, bought 10 of them, quickly integrated, classic use case for lighting automations.

And at first I thought: okay, maybe a bit sensitive. Adjust the calibration, reduce the range, tried everything.

But then reality hit:

The night-time horror

Middle of the night – light comes on. I wake up, fall back asleep. Half an hour later: again. Three, four times per night. After two weeks I was nearly going mad.

I first thought: a bug in my automation. Checked all the logs. But no: the sensor is genuinely reporting motion. Where there isn’t any.

Same during the day. Light comes on when nobody’s in the room. Shadow from outside? Reflection? An insect on the sensor? No idea. But it doesn’t matter – because the result is the same: the system isn’t reliable.

In the video I demonstrate what these false triggers feel like and what impact they have on your trust in the system.

Unreliability is the death of any automation

In my view, this is the death of any automation. Because sooner or later you start disabling automations. Deactivating sensors. You lose trust in the system.

I replaced these sensors consistently with Aqara motion sensors. More discreet, significantly more reliable – and suddenly the system works. No more false triggers. No more waking up at night. Just: it works.

Not a brand problem, but a product problem

Important: this isn’t a general Sonoff problem. I use plenty of other Sonoff devices myself – Sonoff Basic or S20 plug switches for example – flashed with Tasmota. Local, no cloud, rock-solid for years. Except once, a capacitor issue there too – but that stayed a one-off.

The motion sensor is therefore a specific product problem, not a brand problem.

The lesson: test first, then scale up

Test sensors in everyday use before buying ten of them. One sensor for €10 is cheap – but ten faulty sensors are €100 of e-waste.

Unreliable sensors cannot be “optimised”. No tuning, no configuration makes a bad sensor good. Replacing them decisively is the only solution.

Three golden rules for your smart home purchases

From these three fails I’ve developed three rules I explain in detail in the video:

Rule 1: Have an exit strategy

Ask yourself:

Is there a local API?
Can I flash alternative firmware?
Does the device work without internet?

If all the answers are “no” – think very carefully before buying.

Rule 2: Wait for community experience

Wait for long-term reviews. Read user reports. Only install critical actuators where you can reach them again if needed. So junction boxes only with absolutely proven hardware.

Rule 3: Test sensors thoroughly

Testing one sensor in real life for two weeks might cost you €10. Test first, then buy. Not the other way around.

The opposite: the best devices

If you want, in the next video I’ll do exactly the opposite: Three devices that have run absolutely reliably for years. That I would buy again immediately. That cost me zero maintenance.

Watch the video and write “YES” in the comments if that interests you!

Or do you have a smart home device you could throw against the wall? What was your biggest fail? I’m looking forward to your stories in the comments!

Bose Had to Back Down! Open Source Community Saves SoundTouch Speakers

Sun, 18 Jan 2026 00:00:00 +0000

The Turnaround: When Community Pressure Works

Update to my article from November 2025: Remember? Bose wanted to shut down the cloud for SoundTouch, leaving €1,000 speakers stripped of their most important features. Now there’s a spectacular twist!

On January 12, 2026, Golem reported: Bose does a 180° and releases the SoundTouch speakers’ Web API as Open Source. The community has won!

In the video I walk you through the whole story – why this development affects EVERY smart home user, not just Bose owners. Because this is a precedent for the entire industry.

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

What Exactly Happened?

Make sure to watch the video – there I explain all the details. Here are the key points:

1. Bose Opens Up the API

Instead of simply shutting down the cloud, Bose has now released the Web API as Open Source. This allows developers to build their own solutions and use the speakers without the Bose cloud.

Bose’s reasoning: They want to “support the open-source community” and give interested parties “the opportunity to develop alternatives.”

This is a complete reversal from the original “we’re just pulling the plug” approach. In the video I show why this is so significant!

2. More Time for Development

The shutdown was pushed back from February 2026 to May 6, 2026. This gives the community three additional months to develop working alternatives.

3. The App Stays Available

Originally, Bose planned to remove the SoundTouch app entirely from the Play Store and App Store. That was reversed – the app remains available.

The Community Was Ahead of Bose

The most exciting part of this whole story: the open source community was ahead of Bose!

Before Bose even released the API, there were already projects on Github working to keep the speakers usable after the server shutdown. Those projects can now be developed much more easily and reliably thanks to the official API release.

In the video I show you concrete examples of these community projects and explain what this means for the future.

Github projects are already working on alternatives to the Bose cloud – and are now getting official support from the manufacturer.

What Still Works After May?

To be clear – the cloud is still being shut down. In the video I go into detail about what that means in practice:

❌ Gone after May 6, 2026:

Direct music streaming via the SoundTouch app
Reassigning station buttons (existing assignments may continue to work)
Cloud-based services (TuneIn, etc.)

✅ Still functional:

Bluetooth (with the usual range limitations)
AirPlay (for Apple users)
Spotify Connect (if you have a Spotify subscription)
Wired inputs (AUX, HDMI, optical)
Local playback control

Watch the video for a complete analysis of what this means in practice!

Why This Should Matter to You – Even Without Bose

This is the most important message of this article: This story affects every smart home user, not just Bose owners. In the video I explain in detail why this sets a precedent for the entire industry.

Three Important Lessons:

1. Community Power Works

Public attention, critical coverage, and active community engagement can push manufacturers to rethink their decisions. Bose could have simply pulled the plug – but didn’t.

In the video I show how public pressure made a concrete difference.

2. Open Source Protects Your Investments

The more open the systems, the less dependent you are on the manufacturer. Even if a manufacturer drops support, the community can take over the project.

In the video I analyze what this means for your future buying decisions.

3. New Buying Criteria for Smart Home

Before your next purchase, ask:

Is there an open API?
Does an active community exist?
Does the device work locally without the cloud?
Are there already open source alternatives?

In the video I give you a detailed checklist for your next smart home purchase.

What Does This Mean for Other Manufacturers?

The Bose case sends a clear signal to Vorwerk, Belkin, Logitech, Philips, and all other manufacturers shutting down their cloud services:

The community doesn’t give up. If you shut down your cloud, the community will build alternatives. Better to support that actively – the way Bose is doing now.

In the video I explain why manufacturers can actually benefit from this development:

Save their reputation instead of permanently damaging it
Retain existing customers instead of losing them
Build trust for future products

Watch the video for the full analysis!

Practical Tips for SoundTouch Owners

If you own a SoundTouch speaker, in the video I show you exactly what you should do now:

Stay informed: Follow the Github projects and community forums
Test alternatives: Try out Bluetooth, AirPlay, or Spotify Connect now
Support the community: If you can code – join the open source projects!
Be patient: The projects still need time until May 6, 2026

All links to the community projects can be found in the video description!

Conclusion: A Win-Win Situation

At the end of the day, this is a win-win for everyone involved:

For Bose: Cloud costs saved, reputation partially rescued
For users: Devices remain usable, new possibilities through open source
For the community: An important precedent for the future

This shows: Smart home can be sustainable – when manufacturers and communities work together rather than against each other.

In the video I analyze what this development means for the smart home industry in the long run.

Connection to My First Article

This article is an update to: When Your Smart Home Suddenly Gets Dumb – and What You Can Do About It

There I described the problem; here I show the resolution. Exactly how it should work!

Sources and Further Links

Did this article help you? Share it with other SoundTouch owners! For more articles on secure and sustainable smart home solutions, browse the rest of the blog.

Scanne diesen Code
mit Deiner Banking App!

When Your Smart Home Suddenly Goes Dumb – And What You Can Do About It

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

Every Smart Home Owner’s Nightmare

Imagine coming home, opening your smart home app – and suddenly it shows “No Connection.” Not because of an internet outage or a technical glitch, but because the manufacturer simply pulled the plug.

This is happening on a massive scale right now: Bose is shutting down the cloud for SoundTouch, Vorwerk is killing off Neato robot vacuums, and the list grows longer every day. Devices that cost over €1,000 are being turned into expensive paperweights overnight.

But it doesn’t have to be this way! In this video I explain why this happens and how you can protect yourself.

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

Recent Cases: When Smart Homes Go Dumb

Bose SoundTouch: The €1,000 Paperweight

As of February 18, 2026, Bose is discontinuing cloud support for the entire SoundTouch product family. That means:

❌ Spotify integration is gone
❌ TuneIn radio no longer works
❌ Multiroom features are history
❌ App control is heavily restricted

Bose’s explanation: The technology has been “extensively further developed” and the company is “no longer able to maintain the cloud infrastructure.”

Translation: Running the cloud costs too much money.

Vorwerk/Neato: A Broken Promise

Even more egregious is the Vorwerk case: the company had promised five years of cloud operation for Neato robots. Did they keep that promise? Apparently not.

In 2023, Neato Robotics was shut down, and now all cloud services are being terminated. Even robots that were still sold regularly in 2023 are losing their functionality.

Vorwerk’s excuse: “Cybersecurity standards have evolved.”

The truth: They failed to invest in time – or simply didn’t want to.

The Mechanics of the Cloud Disaster

Why does this keep happening? The video explains the vicious cycle:

Phase 1: The Launch

Manufacturer develops a new product
Cloud enables modern features (remote access, updates, etc.)
Sales revenue funds cloud operation

Phase 2: Technical Progress

New device generation requires new cloud architecture
Manufacturer operates two cloud systems in parallel
Double the costs, half the benefit

Phase 3: The End

Old devices no longer sell
Cloud operation becomes a pure cost factor
Pulling the plug is the “economical” solution

Your Checklist: How to Protect Yourself

1. Check Manufacturer Reputation

Before you buy: How has the company behaved in the past?

Are there already reports of discontinued products?
How transparently does the company communicate?
Google search: “[Manufacturer] + cloud shut down”

2. Test Local Features

The most important question: Does the device work without internet?

Can you switch lights on/off during a Wi-Fi outage?
Does the robot vacuum start offline?
Does the heating control run independently?

Rule of thumb: The more features available locally, the safer you are.

3. Question Update Promises

Does the manufacturer specify support periods?

How long will updates be provided?
Are there written guarantees?
Silence is often not a good sign!

4. The Free Cloud Paradox

Warning: Free cloud services are often a red flag!

If a manufacturer only makes money from hardware sales but provides cloud services for free, that model won’t be sustainable long-term.

Better: Transparent subscription models create sustainable value for both sides.

Positive Examples: How It Should Be Done

Philips Hue: Local Foundation + Premium Cloud

Core functions: Fully local via the Bridge
Premium features: Optional via Bridge Pro (one-time purchase)
Transparency: Clear separation between free and paid

Link: Philips Hue Bridge Pro

Aqara: Hub-Based Architecture

Local control: All basic functions without cloud
Cloud access: Optional for remote access and extended features
Fair pricing: Transparent cost structure

Link: Aqara Smart Hubs

What You Can Do Right Now

Immediate Actions:

Inventory: Which of your devices depend on the cloud?
Test: Do they work offline?
Research: What is the manufacturer’s track record?

Before Your Next Purchase:

Prioritize local features
Prefer open standards (Zigbee, Z-Wave, Matter)
Support transparent business models

Long-Term:

Set up Home Assistant or a similar local system
Buy fewer cloud-dependent devices
Factor in community support when making purchasing decisions

The Bottom Line: Your Smart Home Belongs to YOU

As the Süddeutsche Zeitung aptly put it: “Anyone buying technology today is handing themselves over to the manufacturer.”

But it doesn’t have to be this way! With the right preparation and conscious purchasing decisions, you can build a smart home that belongs to you – not to the manufacturer’s cloud.

The full video walks you through everything step by step – from concrete checklists to positive examples to action recommendations for your existing setup.

What do you look for when buying smart home products with cloud features? Have you ever had a manufacturer pull the plug on functionality you relied on?

Write it in the comments – your experience helps others make better purchasing decisions!

Home Assistant Remote Access: Securely Access Your Smart Home from Anywhere

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

Picture this: you’re relaxing on the beach, the sun is shining, waves are rolling in — and suddenly you wonder: “Did I actually turn off the lights?” In the past, that thought would have left you uneasy for the rest of the day. Today, you simply pick up your phone, check Home Assistant, and see immediately: everything’s fine. The lights are off, the doors are locked, the alarm is armed. Welcome to the world of secure remote access!

But beware: the path to this convenience is paved with security traps that can turn your smart home into an open door for hackers. This video shows you how to balance comfort and security.

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

What Remote Access Really Means

The Invisible Bridge Between You and Your Home

Remote access to Home Assistant is like an invisible bridge between you and your home. Whether you’re at the office, on vacation, or just out shopping — this digital connection gives you access to all your smart home’s features at any time.

The key difference from local use: your data travels across the internet. That makes things both exciting and risky. The video gives you a clear picture of how the different connection methods work and where the dangers lurk.

Why Your Smart Home Needs Remote Access

A smart home without remote access is like a sports car without a road — technically impressive, but practically useless the moment you leave the house. Home Assistant’s true power only unfolds when you can reach it from anywhere.

Imagine getting a notification about unusual power consumption while you’re at work. Without remote access, you’re in the dark until you get home. With remote access, you can check immediately, identify the problem, and take action — potentially preventing serious damage.

The Four Ways Into Your Smart Home

Option 1: VPN — The Classic Secure Channel

VPN is like an armored tunnel through the wild internet. With solutions like WireGuard, Tailscale, or OpenVPN, you establish an encrypted connection to your home network. For your phone or laptop, it’s as if you were sitting right at home.

The big advantage: maximum security and full control over your data. The downside: setup can get a bit technical. The video walks you through the most important VPN options and helps you find the right one for you.

Option 2: Home Assistant Cloud — Simplicity at a Price

The Home Assistant Cloud from Nabu Casa is the premium option of remote access solutions: comfortable, reliable, and incredibly easy to set up. A few clicks, a monthly fee of around €5, and you’re ready to go.

What makes it special: no port forwarding required, no complex network configuration. Nabu Casa handles everything. At the same time, you’re supporting Home Assistant’s development, since the revenue flows directly back into the project.

Option 3: Reverse Proxy — For the Tech Enthusiasts

A reverse proxy like Cloudflare Tunnel is the solution for those who like to tinker while still wanting professional-grade security. It becomes particularly compelling in combination with Cloudflare Access, an authentication layer that adds an extra line of defense.

This approach offers maximum flexibility and can be run for free. The setup effort, however, should not be underestimated. The video gives you an overview and points you to a detailed Cloudflare tutorial.

The Path to Disaster: Direct Port Forwarding

There is a fourth option — one I’m mentioning only to warn you against it: direct port forwarding without additional protection. That’s like leaving your front door wide open with a sign that says: “Smart home owner lives here!”

Hackers constantly scan the internet for exactly these kinds of open doors. An unprotected open port is an open invitation for attackers. For more on this topic — and how to do it right — check out my separate video on secure port forwarding.

The Most Common Pitfalls and How to Avoid Them

Pitfall 1: Weak Authentication

“123456” or “password” may be easy to remember, but they’re just as easy to crack. When accessing your smart home remotely, a strong, unique password isn’t optional — it’s mandatory.

Even better: enable two-factor authentication (2FA). Even if an attacker gets hold of your password, they can’t get in without the second factor. The video shows you how to enable and properly use 2FA in Home Assistant.

Pitfall 2: Missing Access Restrictions

Not everyone should be able to access your smart home from anywhere. IP allowlists let you limit access to known locations. Role-based permissions ensure that guests can only see what they’re supposed to see.

These techniques are more powerful than they might seem at first. The video walks you through practical examples and explains how to make the most of these security features.

Pitfall 3: Unencrypted Connections

HTTP is like sending a postcard — anyone can read it. HTTPS is like a sealed letter. When accessing your smart home remotely, always use encrypted connections, regardless of which method you choose.

Creative Uses for Your Remote Access

Smart Heating Control

Imagine you’re returning from vacation earlier than planned. Instead of coming home to a cold apartment, you start the heating from the highway. By the time you arrive, it’s comfortably warm — without wasting energy in the meantime.

Smart Doorbell Monitoring

Expecting a package but still at work? With remote access, you’ll see immediately when someone rings the doorbell. You can talk to the delivery driver, tell them where to leave the package, or even unlock the door if you trust them.

Garage Door Timing

This is one of my favorite use cases: you open the garage door from your car while you’re still two streets away. By the time you arrive, the door is already open and you can drive straight in without stopping. A small convenience that meaningfully improves everyday life.

The video shows these use cases in action and gives you ideas for your own creative solutions.

Why You Should Watch the Video

This article gives you a solid overview of remote access options. But the video shows you the practical implementation. You’ll see:

Live demonstrations of the different remote access methods
Step-by-step guides for setup
Security checklists to work through
Real-world examples of creative use cases
Troubleshooting tips for common issues

Particularly valuable are the security notes that are hard to convey in article form. In the video, you’ll see concretely what to watch out for and how to avoid typical beginner mistakes.

The Home Assistant A–Z Series

This video is part of the “Home Assistant A to Z” series — a systematic introduction to all the important aspects of Home Assistant. Each video stands on its own and can be digested in about 5 minutes.

Whether you’re just getting started or already have experience: this series is guaranteed to offer new tips and tricks. Remote access is a particularly important piece of the puzzle, because it transforms your local smart home into a truly flexible system.

Conclusion: Security Before Convenience

Remote access to Home Assistant isn’t a luxury — it’s a necessity for a modern smart home. But as with all powerful tools: with great power comes great responsibility.

The video shows you how to handle that responsibility correctly. You’ll learn not just how remote access works, but how to implement it securely. Because in the end, the best remote access solution is worthless if it turns your home into an open door for attackers.

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

Home Assistant A-Z: C is for Cloud Integrations

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

Did you know that some Home Assistant integrations can pose real security risks? While you think your smart home is secure, cloud integrations may be sending your most private data to remote servers somewhere on the internet. Today I’ll show you what to watch out for.

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

What exactly is this?

Cloud integrations are Home Assistant integrations that communicate with external servers over the internet. Imagine this: your motion sensor detects movement, but instead of switching your light directly, it first sends that information to a server somewhere in the world — and that server then sends the signal back.

Typical examples are Google Nest, Amazon Alexa, or Ring cameras. These devices require an active internet connection to function.

The opposite are local integrations: everything stays within your home network. Zigbee devices or ESPHome sensors communicate directly with your Home Assistant — no detour over the internet.

Why does this matter for your smart home?

Let’s be honest: cloud integrations are convenient. You can access your devices from anywhere and often benefit from advanced features like voice control. But they also carry risks.

Imagine your Ring camera gets hacked and strangers are watching into your bedroom. Or the manufacturer shuts down their servers and your €500 devices become expensive e-waste — exactly what happened in 2016 with Google’s Revolv Smart Home Hub.

Local integrations, on the other hand, work even without internet, are faster, and your data stays 100% with you. A Zigbee light switch responds within milliseconds — cloud devices often take 100 milliseconds or more. That might sound negligible, but it gets annoying quickly in everyday use.

How does this work in Home Assistant?

How do you recognize cloud integrations in Home Assistant? It’s actually quite simple: look up the integration on the Home Assistant website. There you’ll find what’s called the “IoT Class”. If it says “Cloud Push” or “Cloud Polling”, it’s a cloud integration.

When you install an integration, ask yourself: do I need to sign in with an online account? Does the device need internet to work? If yes, it’s likely a cloud integration.

The most common pitfalls

The first pitfall: blindly trusting cloud integrations. A stark example is Ring cameras: hackers gained access and were able to watch live, speak to residents, and even frighten children. The problem: weak passwords and missing two-factor authentication. Always use strong, unique passwords and enable 2FA wherever possible.

The second pitfall: ignoring vendor lock-in. If Google, Amazon, or other providers change their business strategy, you’re left with worthless hardware. My tip: before every purchase, check whether a local alternative exists. Local devices are often cheaper and more reliable.

The third pitfall: mixing cloud and local devices without network separation. A compromised cloud camera can serve as an entry point into your entire home network. Use a separate guest network for cloud devices, or a firewall to isolate them. There’s more on this topic in another video (add video link in YouTube).

What can you do creatively or practically with this?

My clear recommendation: use cloud integrations only when truly necessary. For voice control with Alexa or Google — fine. But for simple sensors or switches, there’s almost always a local alternative.

If you do use cloud integrations, secure them properly: strong passwords, regular updates, separate network.

My personal favorites: ESPHome for self-built sensors and Zigbee for off-the-shelf devices. Both work completely locally, are affordable, and absolutely reliable.

Next up is “D” is for Dashboard, or take a look at the overview of all A-Z posts.

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

Cloud on Smart Home? Sure — But Secure!

3 Smart Home fails: devices I would NOT buy today!

Fail #1: Shelly 2.5 – When 14 actuators died at the same time

The slow death inside the wall

The same defect – 14 times

Small consolation: repair is possible

The key lesson

Fail #2: Shark robot vacuum – When the cloud kills your integration

From smart home star to useless appliance

One app update. One dead integration.

The moment of realisation

The lesson: an exit strategy is mandatory

Fail #3: Sonoff Zigbee motion sensor – The night-time false alarms

Bought cheap, paid dearly

The night-time horror

Unreliability is the death of any automation

Not a brand problem, but a product problem

The lesson: test first, then scale up

Three golden rules for your smart home purchases

Rule 1: Have an exit strategy

Rule 2: Wait for community experience

Rule 3: Test sensors thoroughly

The opposite: the best devices

Bose Had to Back Down! Open Source Community Saves SoundTouch Speakers

The Turnaround: When Community Pressure Works

What Exactly Happened?

1. Bose Opens Up the API

2. More Time for Development

3. The App Stays Available

The Community Was Ahead of Bose

What Still Works After May?

❌ Gone after May 6, 2026:

✅ Still functional:

Why This Should Matter to You – Even Without Bose

Three Important Lessons:

1. Community Power Works

2. Open Source Protects Your Investments

3. New Buying Criteria for Smart Home

What Does This Mean for Other Manufacturers?

Practical Tips for SoundTouch Owners

Conclusion: A Win-Win Situation

Connection to My First Article

Sources and Further Links

When Your Smart Home Suddenly Goes Dumb – And What You Can Do About It

Every Smart Home Owner’s Nightmare

Recent Cases: When Smart Homes Go Dumb

Bose SoundTouch: The €1,000 Paperweight

Vorwerk/Neato: A Broken Promise

The Mechanics of the Cloud Disaster

Phase 1: The Launch

Phase 2: Technical Progress

Phase 3: The End

Your Checklist: How to Protect Yourself

1. Check Manufacturer Reputation

2. Test Local Features

3. Question Update Promises

4. The Free Cloud Paradox

Positive Examples: How It Should Be Done

Philips Hue: Local Foundation + Premium Cloud

Aqara: Hub-Based Architecture

What You Can Do Right Now

Immediate Actions:

Before Your Next Purchase:

Long-Term:

The Bottom Line: Your Smart Home Belongs to YOU

Share Your Experience

Further Reading

Related Articles

Home Assistant Remote Access: Securely Access Your Smart Home from Anywhere

What Remote Access Really Means

The Invisible Bridge Between You and Your Home

Why Your Smart Home Needs Remote Access

The Four Ways Into Your Smart Home

Option 1: VPN — The Classic Secure Channel

Option 2: Home Assistant Cloud — Simplicity at a Price

Option 3: Reverse Proxy — For the Tech Enthusiasts

The Path to Disaster: Direct Port Forwarding

The Most Common Pitfalls and How to Avoid Them

Pitfall 1: Weak Authentication

Pitfall 2: Missing Access Restrictions