Why Smart Homes Failed to Deliver on Their Promise

Why Smart Homes Failed to Deliver on Their Promise

Despite decades of promises, smart homes remain frustrating and fragmented. This video explores why the dream of a fully automated home has stalled, from incompatible protocols like Zigbee and Z-Wave to reliance on cloud services and walled gardens. The creator tests various systems and finds that even with advanced AI, true integration remains elusive, highlighting a fundamental flaw in the smart home industry.

Why We All Gave Up on Smart Homes. | Transcript:

I had this dream of a smart home cuz we had seen this thing, right? Hollywood had sold it to us. Welcome council. And yet broadcasting beautiful views 24 hours a day. I'm in the future. For good or worse, Hollywood imagined this future with a smart home and tech companies were making it happen. I am putting myself to the fullest possible use. Hollywood has predicted this future maybe too many times. An entire race of machines. So, why are we stuck with this?

Alexa, bedroom lights. A few things share the name bedroom lights. Which one did you want? Uh, much younger version of me made a video about smart homes on YouTube about 7 years ago, and nothing has changed since then. My home doesn't feel smarter. I still need five different apps to manage it. One in three Americans are frustrated about their smart home with Alexa leading the race. So, what the hell happened in a world of AI, of new phones every week? Why does smart home innovation stop? So, I've spent the last few weeks testing, reconfiguring, reconnecting. I've spent far more money than I should trying to figure this out. Is a smart home where everything just works even possible? Is

it my fault? Is it a setup problem? Is it a device problem or a technology problem? Or is that promised smart home just some Hollywood 3? What I found out after all of this is that there is a deeper fatal flaw with what we imagined smart homes could be. And I don't think that tech companies are ever going to be able to solve it. There is a way. It just requires you to jump into a rabbit hole with me. There's something that we need to get out of the way first, which is that smart homes are not for everyone. Cuz there are smart home users and there are smart home users. Now, before I started making this video, I consider myself somewhere around there in this

scale. I could set up my own Wi-Fi, my Alexa, my smart stuff. But if you click this video, I'd expect most of you watching are somewhere on the right side of this scale. But to build that smart home that I dream of, that smart home that Hollywood made me imagine, I had to level up. But see, that's also the first problem with our smart homes today. Setting them up, it's our job. And that's not how smart homes started at all. cuz we've had smart homes since the 70s. It's just that they weren't built for us. Take this thing for example. This is a Cresten Isis TPS 6000. This was one of the first modern home control hub systems and it was released around the year 2000. And check it out.

It had a 15-in touchscreen. It could monitor audio and video sources. It could control your lights and your drapes. Could check security cameras all on this screen. And this is in the '9s, almost 10 years before the iPad. But if you could get that thing to work 30 years ago, why does Alexa struggle to turn on a light? Good morning. Who is she? That's the voice of our computer. Well, does she cook as well? Not yet. Yeah. Well, those things, yeah, they existed in the '90s, but they were closed system. Most of the devices either came from the same company or companies that were closely working together, and that's what made this

experience so seamless. but they were expensive. So, a pro-installed complete Cresten style system today can cost 20 to $100,000. And you were of course locked into that company. Those millionaires with their smart homes, they've always been the user. Like, anyone can run a smart home if somebody else sets it up for them. But for today's smart homes, we are expected to do the setup and the maintenance. I've often felt that I've spent so much time getting this thing to work that by the time it works, it's not even worth the effort. The fact that we're expected to do this ourselves, the fact that this needs to be end user friendly, or at least try to be, well, that's the beginning of our problems.

Open the pod bay doors, Hal. Alexa, open the door. I'm not quite sure how to help you with that. So, why can't this extremely simple command work? Alexa should be able to send a signal to the lock, right? The website says that it supports Alexa. I know I set it up correctly. Like, I know this is actually working. I got it working last week. Siri, who's even dumber than Alexa, can actually open my door. Siri, open the front door. See? So, when I talk to Siri on my phone, my phone is going to try to reach the lock directly. It's going to try to do it via simple, straightforward local Bluetooth like this. But if I'm not at home, then my request is going to have to go

through Apple's servers and then through my Apple TV, which in this case kind of works like a hub that forwards the signal from the cloud to the lock. Now, just the fact that plan A is this signal being sent locally here in my house, that's huge. that's fast, that's efficient. Plan B is okay. I guess it's possible thanks to Apple's framework. I'm going to explain what a framework is in a sec, so don't worry about it. But Alexa, Alexa can't do this stuff. So, when I ask Alexa, my request can't go directly to the hub. It needs to make the journey from the speaker to my Wi-Fi to then go to the Amazon server so that it can interpret what I said. and then through the Alexa skill by Aara that makes a bridge to the

Accara cloud which then sends a signal back to my Wi-Fi and then to the Accara hub so my open door signal can finally make its way through the lock using Sig as the last step. This is a mess. This is just one device. Each of those connections is a failure point. Something might not work which explains why this counter has never gone about like 3 days. On the other hand, Hal, good evening, Dave. How you doing, Hal? Everything's running smoothly. And you doesn't need any of this stuff. Like, he is directly wired to everything.

This mission is too important for me to allow you to jeopardize it. Hal is not only wired, probably by cable to anything. Like, all devices were designed to work on this ship. A big underestimated challenge with smart homes today is that you need to get all these devices that come from all of these different companies and get them to work together and to message each other through a bunch of different networks. Just in our lock example, we've already seen Wi-Fi and Bluetooth and ZigG, and those are just a few. These devices not only don't speak the same language, but they don't want to speak the same language. Like this isn't an Alexa or an Apple HomeKit problem.

Smart homes have been trying to deal with this thing for over 50 years now. Like I said, there is a solution to this. But to get there, I first had to understand what was wrong with our current tech and how we ended up in this mess. All the way back in 1975, this company called Pico Electronics came up with this first the first consumerfacing smartome protocol. No Wi-Fi, no Ethernet, no hubs. It used the power cables, the electricity cables that you already have in your walls. What Extend did was piggyback tiny bursts of data directly onto the AC alternating current power line. So you had these 120 kHz bursts that were timed right around the zero crossings of the 60 Hz waveform in your electricity. It worked for Europe as

well with 50 Hz and 100 kHz. This is actually really clever. So, a motion sensor could turn on a light using this technology, even if those two devices were from different brands. Even if this was the 70s, as long as they both spoke X10, they could understand each other. We are all by any practical definition of the words foolproof and incapable of error. X10 was the first time that normal people, not millionaires with custom installs, could actually automate their homes. By the way, normal people is a bit of an overstatement. It's not like this guy could have figured this out or set this up himself. But I'm going to get back to this. An X10 was insanely clever, very primitive, and with a few problems. It wasn't easy to use. It

often failed because the power lines were very noisy. Stuff like your microwave or your hair dryers could mess up the signal and you could only fit a really small number of devices. It was very slow cuz you could only synchronize it to the power waveform. So you really got only about 60 bits of raw data every second. And if your neighbor had X10, well, there wasn't any encryption to protect you. So his system could very well interfere with your lights. But we have to respect X10 because they were the first. This is true retro tech. And dozens of alternative protocols have come in the years after, and every single one of them solves a problem, but also creates

a new one. Now, Z-Wave came in 1999, and it was revolutionary because it was wireless. With a Z-Wave hub at the center, you could send signals to devices up to 100 meters away. The problem with Z-Wave is that it was still kind of slow. It was expensive. It's still expensive today. But then along came Ziggb, which we already touched on. ZigGB is what my smart lock is supposed to support. Now, ZigGB introduced mesh networks. So, you still needed a hub at the center to send all the instructions, but if devices were outside of the range of this main hub, they could relay messages to each other, which is very clever on paper, but an absolute mess in practice. I'm going to get to that. And then came Thread and HomeKit Protocol and Bluetooth and

Matter. So, who can keep track of the difference between all of these? But if you ever dream of that Hollywood smart home, you have to know. And if you already do, you probably know where this video is going. Don't worry, we'll get there. But most of us don't, or I guess didn't. Take this guy over here. He's something like my mom. My mom can't afford those fancy millionaire systems. She can't set this up herself. Heck, I still need to go to her place to repair the Wi-Fi or the TV settings when they break.

Wake up, Daddy Sh. Welcome home, sir. Congratulations on the opening ceremonies. That was such a success. Now, Hollywood might still have planted that dream in their heads. In the 2010s, for example, it almost looked like it was going to happen, like smart homes were happening. And then Alexa came around. Is it on? Oh, it's always on. Can it hear me right now? Can hear you from anywhere in the room. I enjoy working with people. These guys, they might have watched a Super Bowl ad and maybe they were convinced to buy into it, but that bubble pops the moment you have to set up your first device.

This may feel like a no-brainer to you people on the right side of the scale, but for most people, Alexa is this nightmare, frustrating experience. 9.6 out of 10 in that frustration scale. It is not easy. Now, a few people realize that we've reached this point in AI where we actually don't need to rely on the not so great solutions that these big tech companies give us. Platforms like Emergent actually let you build your own solutions now and stop depending on expensive SAS or products that harvest your data. Emergent is an AI app builder where you describe what you want out loud and it actually builds it for you like a real

conversation. And it's not just a web app. Emergent can build native iOS and Android apps. It can connect to Stripe. It can handle authentication, multi-tenant data, all from a single prompt. Build me an app that shows my calendar meetings for the day, my top unread emails, and daily Stripe revenue all in a dashboard and deliver it at 8 in about 30 minutes with no backend setup, no separate API accounts. It was just done like 3 years trying to get Alexa to open a door. 30 minutes to build a custom dashboard that I actually use every morning. Now, if you have any type of software idea, tool for your business, client portal, something

that you're currently paying $80 a month for that you could just own, Emergent is worth trying. They sponsored this section of the video. There's a link in the description if you want to try it out. Now, that didn't stop this boom of IoT around 2015. The internet, everything can all integrate and work more efficiently, connected through 5G technology changed the way that you and I live. era of the internet of things is quickly approaching. Our company was around back then. I remember every other pitch deck I saw was about some IoT smart sensor or smart device. For a startup in 2015, saying IoT was like saying AI last year. Like money was pouring into these companies.

Everything was going to be connected. Beacons and NFC tags. Finally, smart everything. road. Hello, Mr. Yakamoto. Welcome back to the gap. At the start, I was hooked and I was ready for my smart home. And I like we all were like smart speakers became a billiondoll industry in no time. By the end of the decade, 30% of US households had a smart speaker. Amazon was selling these things practically at a loss just for the odd chance that you'd order some stuff on Amazon through them. Our smart home dream was about to finally come true. And with smart speakers, well, now we just need smart devices. And this is where the bubble started popping. This is where we saw what owning a smart home was really like. And it wasn't pretty.

Take Iris for example, a set of smart devices released by Lowe's and really the epitome of everything that's wrong with smart homes today. Now, Iris smart devices used to run over the Ziggb and the Z-Wave protocols. So, I guess it's about time I explain what a protocol means. Now, a protocol is a set of rules for how devices talk to each other. It's like a language that devices used to speak. Now, ZigGB, for example, speaks over the 2.4 GHz frequency, which is the same frequency that we use for Wi-Fi, which is kind of another protocol. Now, Bluetooth is also a protocol. It's another language that also happens to work around the 2.4 GHz frequency. So all of these three, they overlap. They overlap and they crowd that 2.4 GHz frequency, which is

the cause of many of our problems. Like even though the language is different, when you have all these devices in the same place speaking over the same channel, they are going to interfere with each other. Now, we might not see those errors daily, but they do translate into drop packets of data, bad connections, slower speeds, and the occasional reset on my little tracker thing. Now, Iris also supported Z-Wave. Despite being the oldest of the bunch, Z-Wave worked at a frequency of 800 to 900 MHz, which is kind of around here in the spectrum, and that gave it a much longer range, but a slower connection.

Now, the thing with Z-Wave is that it's still around. People use it. It's just not used as much in homes as Ziggp. So, anyway, we've established that the band is the highway and the protocol is the language through which we speak. So, how do we control them? By the way, we've now entered a realm of stuff that I had heard about before I started researching this video, but that I didn't really understand. And that is kind of the thing. If you want a smart home, you have to be one of those guys. Remember that Lowe's Iris smart devices ran on a Ziggb network. So Lowe's had this central hub device that would send messages to all of the devices. And again, because Ziggb is a mesh network, those devices could relay

messages if needed. Now, for you to talk to that hub, you could use the Lowe's app, which is great, right? Well, their app worked great for Lowe's devices under the Lowe's hub, but it couldn't talk to other devices. No, no, wait, wait. I just said that ZigGB is a language. Everyone on Ziggb speaks Ziggb, don't they? Well, not really. If you bought, for example, a Staples smart plug, even though it also ran on Ziggb, it didn't necessarily talk to Loza's hub. Or I should actually say it didn't want to, cuz to control Staples devices, you needed the Staples hub and the Staples app. And even though they're both operating on Ziggb on the same channel, the same highway, the same protocol, devices

speak the same language. No, you could not control Staples devices using the Lowe's app. Why would companies not make this thing cross-co compatible? Just save us all a headache. So, how about smart speakers? Are those the solution? Now, Alexa in this case operates like a framework. A framework like Alexa or Google Home or Apple HomeKit. It's it's this layer that tries to connect all of these devices together. Devices that may work on the same protocol or even across different protocols. Now, a framework is also not just the app that controls everything. It's an app that adds a layer of automation or room combinations. And Amazon Echo have a Ziggby hub. We can use that, right?

Right. Well, not always. Not always cuz you have different versions of Ziggb and different versions of Echos and not all of them have a Ziggby hub. Even worse, your smart device might be designed to require a hub that's made by its own manufacturer. It makes a difference if you already connected this device to its own hub and you're trying to connect it to Alexa devices managed by Do you see where I'm going with this? Nobody can keep up with this stuff. Nobody. And to make matters worse, both of those examples I just gave you, Lowe's Iris and Staples, they have discontinued their smart devices. So what happens then? Often times devices just turn into bricks. Really expensive bricks at that cuz you just can't use

them anymore. app discontinued, hub, discontinued, like these walled gardens that companies create, they never consider the possibility that the company might go under or they just don't care. And so why do these smart home companies die all the time? Well, part of it is that making smart home devices, h it's not really a great business. Look at the business of selling smartphones. These are $800 to$1,000 devices that could last that are supposed to last four to five years, but the company often manages to convince us to replace them 2 years in even though we don't really need one. They've even turned renewing iPhones into a subscription now. Now, on the other hand, look at a smartome device. This is maybe a $50, maybe$1,

$150 device that you are not going to replace until it breaks. Could be years, could be 10 years. Given my smart home is largely unchanged over the past four years, they've proven to be a reliable foundation. I've had this guy for a few years and it's been rock solid. So, I've kept it. I've had it for 3 and 1/2 years. Still works great. And we're still using HomePods for the speakers on the Apple TV and they've been working great. Like, not even the smarthome YouTubers are replacing these devices. It's not a recurring business and it's not a high margin business either. It does remind me a bit of the light bulb companies with the whole feeas cartel mess. In the 20s and

30s, like all the light bulb companies in Europe and in the US, they got together and they agreed to reduce the life expectancy of light bulbs from what they could be, which was about 2500 hours to about 1,000 hours. So, you needed to buy more light bulbs. Cuz again, just like with smart devices, selling light bulbs every 2500 hours is not so great of a business. And that explains why some smart devices feel so overpriced, right? It's a simple plug, right? It should be worth 10 bucks, five bucks. Oh, it's worth 40. Well, cuz the margin needs to come from somewhere. But that pricing was also a gateway for their own doom. Competition from China cuz Chinese smart devices are cheap and so they compete. So why would a western

company want to get into this business? It's kind of this self-fulfilling prophecy, right? People grow tired of these protocol hiccups. They stop buying devices. Companies die. Devices turn into bricks. People get more tired. Loop starts again. That's where we are now. It's 10 years later. We're stuck in a loop. there is no real motivation to level up the quality or ease of use or to innovate. He had received um audio files recordings from what was going on in our house. You could argue it's even worse now because so many IoT devices have shown us their true colors and it's not pretty. Alexa recordings leaking online.

We looked twice at this Internet of Things revolution and realized that having all these cameras and microphones and sensors in our home, all connected to the internet, all managed by different companies, maybe it's a little dangerous. Maybe we don't want a connected fridge that one day randomly decides to play ads. Maybe we don't want an AI in our homes listening to everything. That's it. That's the answer. Smart homes are stuck between a rock and a hard place. It's a nightmare of protocols that few people can make sense of and a bad non-recurring business that companies don't want to get into or that have to compensate by selling your data or ads or subscriptions. But the dream is not debt. Like researching this video

has brought me close to another group of nerds. A huge group of nerds that I think still believe that this Hollywood smartome future is possible. a smart home that doesn't rebel against you or that uses your conversations to advertise you. It's possible and I believe that it is. But for them, but if you're with me to this point in the video, well, I've sort of tricked you into understanding the basics of protocols and frameworks. Now you know what Ziggb means and how it's different from Z-Wave. I tricked you into leveling up in our scale. And now I can give you the solution that I found. I give you guys Home Assistant. Really?

All this fuzz about Home Assistant. Who doesn't know about Home Assistant? Well, I didn't know. I had no idea before I started making this video, but it's a thing. And for the past few weeks, I've been leveling up and I've been setting it up in my own place. So, every smart home video I found online, every review, automation tip, hack, everything led to this platform, Home Assistant. So, I had to try it myself. So, this is by no means sponsored or paid. I've done the work and I've been setting up Home Assistant in my house. The story is that this dude Pablo Schzen started tinkering with his set of Philips Hugh back in 2012.

His tinkering evolved from just a few lines of code of Python to an open source GitHub to a project to a platform to an operating system and now a literal nonprofit foundation. Like for many years, the nerds that kind of nerds built it. thousands of forks on GitHub, the second most active open-source project on the platform. And slowly but surely, documentation made it to a point where normies like me could mostly use it. But the problem is you have to do this stuff yourself. That immediately means that smart homes, they're just not for everyone cuz you actually need to level up to build a smart home or to set up one for your house. Like hopefully this video has helped out a little bit. Now

the big perk about Home Assistant here is that it can run locally. So remember that Amazon Alexa diagram I did earlier that had to go through all that cloud processing. Now Home Assistant is not in the cloud. It's like an operating system for your house and you don't even need to connect it to the internet if you don't want to. So the most complicated part which again nerds will probably find very easy. It's not for everyone is installing this operating system. You can do it on a Raspberry Pi, which I guess is like three out of four in the scale of difficulty. Um, you can install it in an old laptop running a virtual machine, which is what I did. And more recently, you can also use this thing.

This is like Home Assistant's own computer, which you can buy for like 150 bucks. So, Home Assistant is open source. It's free. It is really free. It supports everything. As of April 2025, about 2 million households use Home Assistant. It operates under this nonprofit open home foundation which is partially funded by another branch of the company that's called Nabukasa. So Nabukasa um makes money from stuff like the home assistant green that's like a for-profit branch and they also make money from stuff like this. This thing for example is a Ziggb/Thread antenna or a router. It's kind of like the equivalent of that HU hub or that Iris hub. So this device talks to all ZigGB devices. I actually got rid of my Hue hub and connected all of my Hue

lights directly to Ziggbby and all the other Ziggby devices in the house. They're all connected to this antenna. So, Home Assistant is running here on a virtual machine, I can access it from a browser, from a phone app, which is just connecting to this local computer. The big advantage of all of this is that because this platform is open source and honestly also because of the hard work that these guys are putting in, they've integrated to everything. There are 3,400 plus integrations on the last count. Some are community built. Some companies are already building their own on the platform. And with a single Ziggbby hub, you can pretty much ignore all the other hubs from other devices

and connect everything to this one. So no more translation or no more skills integration. Everything runs together locally. Now this also supports Thread, which is the most recent complication of smart homes. Definitely built with best intentions. There's great potential, but it's one more protocol that we have to be compatible with and understand, especially now that thread and matter are popping up in devices everywhere. Now, remember that we said we have hubs on one side and devices on the other. The channel is the 2.4 GHz network where they operate and ziggb on top of that was the protocol. But in reality, ZigGB was two things. First, ZigGB is the mesh

network. Remember that network that can relay messages to each other even if they're they're out of the range of the main hub. And second, ZigGB was the language that these devices spoke. Okay, so you might have run into these logos more recently. So what's up with those? Now, just to screw with our brains a little more, Thread is a new network layer, which is similar to what ZigGB did. Now the big practical advantage beyond other technicalities is that instead of depending on one hub, a network can have a backup, multiple hubs. In this case, they're called leaders, which is useful when one of them fails. Now the confusion part is that thread is not the full protocol.

Thread is just the network part. So this would be incorrect. Thread still needs a protocol. And in this case, the most popular one is matter. Now matter works over the thread mesh network. It's two different things. Well, ZigGB does both of these things in one name. Now, the big advantage of Thread is that it connects more directly to other devices in a network in like an IP network versus Ziggby, which always has to go through the framework of the app controlling the hub. But back to Home Assistance, like once you have a Home Assistant OS running, you can plug one of these or one of the dozens of Ziggb and Thread

antennas that you can find on Amazon and basically make that your hub. Home Assistant is a framework that connects directly to all the protocols and it does things locally. Now, some examples of stuff that I've built. First of all, I really like physical buttons and think they're important. So, I installed a couple of these around the house. We use it for stuff like dinner time. So, there's button number two is dinner time that is connected to an Apple Music playlist. So, when you hit it, lights get set in like dinner mood and there's a playlist that we all contribute to that starts playing immediately. We have like an automatic dimming as it gets dark like I think 1000 p.m. lights start sort of

transitioning like winding down sort of lights and start getting darker until they shut down completely around midnight. One of my favorite automations is I connected my balcony lights. I wrote a script that gets tomorrow's weather forecast and puts it in the lights. So I have four lights, morning, noon, afternoon, and evening. So you get yellow for sunny, white for cloudy, and blue for rain. I think I set purple for thunderstorms, but it hasn't happened yet. But that's that's really cool. I get the forecast without even checking. Uh my favorite by far my favorite is I have this NFC tag hidden on top of that speaker. What happens is you tap it with your phone.

It automatically sets the house to movie mode. And movie mode is like this 4hour setting where turns off all the lights or sets them to like the absolute minimum brightness for some of them. Uh just enough so you can kind of find your way. But if you pause the movie, all the lights increase in brightness a little bit. So that lets you kind of find your way to the bathroom or grab a snack. And then when you play the movie again, all the lights dim again. And when the movie's over, you turn off the TV, the lights boot back up, so you can kind of find your way. Now, the last experiment that I've been running, and maybe I'm going to be judged for this a little bit is I installed OpenClaw in the computer that runs Home Assistant. Now, OpenClaw

is this opensource agentic AI that Silicon Valley is going crazy about. That's a video for another day. We actually made that video if you want to check it out. But thanks to that, I can do stuff like this. Hey, Hal. So, uh, I'm throwing a Halloween party tonight. Um, and I want you to come up with like the spookiest possible setup for all the lights in the living room and the balcony. You're also trying to impress some of our YouTube subscribers. So, uh, go nuts. Take that, Alexa. Now, ironically, I called this whole thing hal, which I really hope, really, really hope doesn't backfire, but this is all possible and not crazy risky because of the local nature of both of these things, right?

So, this is Home Assistant running locally. OpenClaw, which also runs locally. It lives, they both live in the same laptop, old laptop that I repurposed, and they're connected together via Home Assistant's API. Hal doesn't have access to the internet except for receiving and sending messages, which I get via iMessage. So this again would be much more dangerous if for example I was using Alexa. There's a company on the other end that's listening to your conversations that's gathering your data and harvesting and using all this data for whatever right but this local model runs under APIs that I control that I pay for and therefore are not harvested for data and stuff like the voice translation. I even do that in the

computer because it's it's like really lightweight AI. Something like this could be the future. a local smart home that learns from your patterns and automates based on that. I actually asked Halle to like do a review of stuff that happened and find patterns that we could automate. For example, I discovered the other day that whenever you pause a movie, if you're in movie mode, the bathroom light turns on immediately after it has a sensor. So, why not automate that? So, it's kind of observing those potential automations, which for now are mostly light patterns because that's what I mostly have. But, I think that we're on to something here. And there is no bas spying on me.

There's no connections that have to go through the cloud. Everything is happening here in house like the real how. Good afternoon, Mr. Amr. Everything is going extremely well. Now, just to be safe, by the way, just to be safe, the whole system has no control over the front door lock, which is smart, but it's the only smart thing in the house that's not connected to anything. We'll get there. We'll get there. Baby steps. Remember everything that has hindered smart homes over the past decade. The fact that we have too many hubs, too many apps, that we have useless devices whenever a company goes bust or that our data has to go to the

cloud, that everything exists in these walled gardens. Like this could be the solution to that. All we need to accomplish this is devices. Hopefully, hopefully now with stuff like Home Assistant, hardware companies can stop focusing their time on building new apps and building new hubs that only control their stuff. they can get on this boat and focus that time on the hardware innovation part. It's 2026. We should be past curtains and lights and plugs that we have to create rules for. I've spent hours configuring all this stuff. It has not been easy. Get me smart local AI rules that learn for my behavior. Get me a smart kitchen that cooks for me.

This detects what you're craving and makes it for you. Enjoy your dinner. Now, Hollywood did predict that Maya Hal might go rogue. And that is a risk that I'm willing to take, you know, in the purpose of this experiment. But all of those Hollywood ideas, they never ever predicted this terrible reality that we live in now, which is that companies might invent smart stuff in order to harvest your data. A and that's just a grimmer version of a future that I think Hollywood failed to predict. Now, this big remodeling that you saw as we were doing this video, it actually has to do with another catastrophic issue I found in my house. There's something very wrong about my TV settings, and I think your TV might be suffering the

same fate. We made a whole video about it. You should check it out. Catch you in the next one.

More Tech Transcript