Data Security on Smart Home? Sure — But Secure!

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 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

Backing Up Home Assistant to Google Drive

Thu, 03 Apr 2025 00:00:00 +0000

My first backup video used Microsoft OneDrive as the example. After that, many comments came in with the same question: And how does that work with Google Drive? Fair enough – not everyone wants to use Microsoft. So here’s the answer.

The good news upfront: Home Assistant encrypts its backups by default before they reach the cloud. That means neither Google nor Microsoft can read the contents. This makes storing backups on a third-party service perfectly acceptable from a privacy standpoint – and takes the wind out of one of the most common objections.

The setup with Google Drive is more complex than with OneDrive, however, because you need to complete a few steps in the Google Cloud Console. I’ll walk you through all of them.

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

Home Assistant Backups with Google Drive

In my previous video on backups, I introduced the new backup mechanism in Home Assistant starting with version 2025.1 and demonstrated – using Microsoft OneDrive as an example – how easy it is to store encrypted backups at a secure second location using the built-in options. The Microsoft OneDrive integration in Home Assistant is very straightforward, but not everyone wants to use OneDrive.

So in this video, I want to show another popular alternative: integrating Google Drive into Home Assistant, step by step. The initial setup is more complex than with OneDrive, so I’ll walk through the entire process.

By the way: since Home Assistant encrypts its backups by default, storing such sensitive backups on cloud storage from Microsoft or Google is not a privacy concern at all, and can in my assessment be done without hesitation.

If you’d like to familiarize yourself with the basics of the new backup mechanism first, I recommend watching this video before continuing. In the following, I’ll focus exclusively on integrating Google Drive into the backup mechanism and won’t repeat the general overview of Home Assistant’s backup system here.

Prerequisites

You’ll need a Google account to get started. Your Home Assistant installation also needs to be running a version that supports the new backup mechanism, i.e., version 2025 or later.

What you need to set up in Google and why:

For Home Assistant to communicate with Google Drive, you need to create the following elements in the Google Cloud Console:

Google Cloud Project
The project is the container where all configuration for your Home Assistant connection is collected. You can manage specific settings and all access centrally here.
OAuth Consent Screen
This step is required to identify Home Assistant as an application authorized to communicate with your Google Drive. Here you define basic information about the application, such as name, email address, and access permissions.
OAuth Client (Web Application)
The OAuth client is the access key that Home Assistant uses to authenticate with your Google account. It consists of two parts: the Client ID and the Client Secret. These are entered into Home Assistant later.
Google Drive API
This API allows Home Assistant to access your Google Drive and store or retrieve files there. It must be explicitly enabled for the connection to work.
Test Users
Since your application is not verified by Google, you need to add your own email address as a test user to gain access.

Integrating Google Drive into Home Assistant

In your Home Assistant installation, go to Settings and then Integrations. Click Add Integration and search for the entry Google → Google Drive.

The setup wizard that follows will ask you for a name (which you can choose freely), as well as an OAuth Client ID and an OAuth Client Secret.

In the upper section of the setup wizard, the necessary links are provided for creating this ID and secret. Let’s take a closer look at those now.

Click the OAuth Consent Screen link and sign in with your Google account if you haven’t already. You’re now in the configuration area of the Google Cloud, in the Google Authentication Platform dialog.

Creating a Google Project

If you’ve never been here before, you need to create a project first.

Click Create Project and give your project a name, for example Home Assistant Backup.
Click Create and wait a few seconds for the project to be created.

Registering an OAuth Application with Google

Creating the OAuth Configuration

You’ll now see the OAuth Overview screen with a notice that the Authentication Platform has not yet been configured.

Click Get started.
Enter a name for the app, for example Home Assistant or Home Assistant Backup.
Under User support email, select your email address from the dropdown menu and click Next.
Under Audience, select the option External and click Next.
Under Contact Information, enter your Google email address and click Next again.
Confirm the User Data Policy with a click and select Continue.
Click Create.

Google will now confirm with the message OAuth Configuration Created that everything was set up successfully.

Creating an OAuth Client

On the screen shown, click Create OAuth Client.
Under Application Type, select Web Application.
Leave the name as Web Client 1 or enter a custom name like Home Assistant Backup.
Scroll down and under Authorized Redirect URIs, click the Add URI button.
Paste the address that Home Assistant shows you in the setup dialog under Step 5.
Click Create.

Google will now display the generated Client ID and Client Secret. Copy this information and paste it into the Home Assistant setup dialog.

Configuring Audience and Test Users

To actively use the authentication, you still need to add your email address as a test user on the Google side.

In the Google Cloud Console, navigate from Clients to Audience in the left sidebar.
Scroll down to Test Users.
Click Add Users and enter your Google email address.
Confirm your entry.

Enabling the Google Drive API

Before everything works, you need to enable the Google Drive API in the Google Cloud Console so that Home Assistant can use it after authentication.

In the Google Cloud Console, switch from Google Authentication Platform to APIs & Services in the left navigation bar.
Click Enable APIs and Services.
Type Drive into the search field.
Select Google Drive API from the search results.
Click Enable.

This may take a few seconds. Afterwards, you’ll be redirected to a screen showing details about the Google Drive API usage.

Completing the Connection with Home Assistant

Return to Home Assistant and click Open Website.
Select your Google account again if prompted.
Confirm Google’s warning that this application has not been verified by clicking Continue.
On the next screen, confirm that you want to link your Google account with Home Assistant and click Continue.

At this point, a wizard to open My Home Assistant Links may appear.

Enter your Home Assistant URL once and confirm with Save.
Finally, the prompt Link Account Home Assistant will appear, which you can confirm by clicking Link Account.

Completing the Setup in Home Assistant

Return to Home Assistant, where you’ve already entered the API Key, OAuth Key, and Client Secret.
Click Open Website.
Select your Google account and confirm that the app has not been verified by clicking Continue.
Confirm once more that you want to proceed with the configuration.
Finally, click Link Account.

If everything has been set up correctly, you’ll receive a Success message in Home Assistant confirming that the Google Drive configuration has been created.

Configuring Backup Settings in Home Assistant

You can now – as you may already know from the previous video – go to Settings > System > Backups, then Backup Settings > Backup Locations and enable Google Drive there.

From now on, your backups will be saved not only locally, but also to Google Drive.

→ If you want to understand why it’s important not to rely solely on manufacturer clouds, this article is worth a read: Wenn dein Smart Home plötzlich dumm wird – und was du dagegen tun kannst

Home Assistant Backups in 2025.1 – Your Data Safe and Recoverable at Any Time

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

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

Why Are Backups Important?

Imagine your Home Assistant system stops responding. Your automations, devices, and integrations are gone — everything you set up over months or even years, lost. That thought alone is unsettling, isn’t it? But that’s exactly what can happen if you don’t make regular backups.

Fortunately, Home Assistant version 2025.1 introduces an improved backup system that is simpler, more secure, and more powerful than ever before. In this article, I’ll explain why backups are essential, how to set them up in Home Assistant, and which strategies you can use to best protect your data.

What’s New in Home Assistant 2025.1?

The new backup feature makes it even easier to secure your installation. Here are the key improvements:

Automated backups can be scheduled directly within the system.
Cloud storage without extra add-ons — now directly to Google Drive, Microsoft OneDrive, or a Synology NAS.
Encryption by default protects your backups from unauthorized access.
Easy restoration — regardless of which installation method you use for Home Assistant.

This eliminates the need for external scripts or community add-ons to create regular backups.

Comparison: Old vs. New Backup Method

Previous Method

In the past, the backup functionality in Home Assistant was fairly rudimentary. You had to trigger backups manually through the interface or rely on add-ons like Google Drive Backup to store backups automatically in the cloud. A simple, integrated solution for regular, secured backups simply didn’t exist.

New Method in 2025.1

With the new backup feature, you can:

Run backups automatically on a schedule
Store backups directly in the cloud, without third-party add-ons
Selectively back up or exclude specific components
Perform an easy restoration with just a few clicks

In short: it has never been this easy to secure your Home Assistant system!

Step by Step: How to Create a Backup

Watch the video above for a detailed walkthrough of the process.

Tip: Occasionally test the restoration on a separate system to make sure your backups actually work.

Backup Storage Locations – What’s the Best Option?

Home Assistant 2025.1 offers various options for storing your backups:

Local (SD card or SSD) → Quickly accessible, but vulnerable to hardware failures.
Cloud (Google Drive, OneDrive, Synology NAS) → Safe from hardware issues, but dependent on internet access.
Hybrid solution (local + cloud) → The best strategy for maximum security!

Recommendation: Keep at least 7–10 backups to have multiple restore points available.

Best Practices for Your Backup Strategy

To make sure you’re always on the safe side, keep these tips in mind:

✔ Schedule regular backups: Daily or weekly, depending on your usage. ✔ Use encryption: Especially when storing backups in the cloud. ✔ Diversify backup storage locations: Local + cloud for maximum security. ✔ Store important passwords securely: Especially for encrypted backups.

Conclusion: Backups Are a Must for Your Smart Home!

With Home Assistant 2025.1, there are no more excuses to skip backups. The new features make securing your system enormously easy and turn restoration into a breeze when things go wrong.

Try out the new backup feature and make sure your smart home stays protected at all times!

Backing Up Home Assistant to Google Drive – Step-by-step guide to the Google Drive integration, including OAuth setup
Cloud vs. Local – What You Need to Know About Storing Your Data – Why local backups alone aren’t enough and when cloud storage makes sense

Data Security on Smart Home? Sure — But Secure!

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 A-Z: C is for Cloud Integrations

What exactly is this?

Why does this matter for your smart home?

How does this work in Home Assistant?

The most common pitfalls

What can you do creatively or practically with this?

Backing Up Home Assistant to Google Drive

Home Assistant Backups with Google Drive

Prerequisites

What you need to set up in Google and why:

Integrating Google Drive into Home Assistant

Google Cloud Platform Login

Creating a Google Project

Registering an OAuth Application with Google

Creating the OAuth Configuration

Creating an OAuth Client

Configuring Audience and Test Users

Enabling the Google Drive API

Completing the Connection with Home Assistant

Completing the Setup in Home Assistant

Configuring Backup Settings in Home Assistant

Home Assistant Backups in 2025.1 – Your Data Safe and Recoverable at Any Time

Why Are Backups Important?

What’s New in Home Assistant 2025.1?

Comparison: Old vs. New Backup Method

Previous Method

New Method in 2025.1

Step by Step: How to Create a Backup

Backup Storage Locations – What’s the Best Option?

Best Practices for Your Backup Strategy

Conclusion: Backups Are a Must for Your Smart Home!

Related Articles