Calvin Wankhede / Android Authority
Building a smart home is a great idea. why? People often say that home automation makes your life easier.
That may sound appealing, but I'm not sure I completely agree with that statement. I've tried countless automation products over the years, some of which were crappy and shouldn't even be connected to my home network.
My family is certainly a lot smarter now, but back then it was a fierce battle. With so many standards, brands, and even communication protocols, it can be difficult to get a consistent experience, even for technology enthusiasts.
I can't distill everything about my journey, but I can save you from having to go down a particularly dangerous rabbit hole. To that end, here are five lessons I learned from building my own smart home that might help you build your own automated paradise.
1. Wi-Fi sucks – try Thread, Zigbee, or Z-Wave instead
Calvin Wankhede / Android Authority
Connectivity is at the heart of a smart home, so let's talk about it first. There are four main smart home networking protocols in use today: Wi-Fi, Thread, Zigbee, and Z-Wave.
Thread, Zigbee, and Z-Wave enable mesh networks. This means that devices can directly exchange information with each other and relay point-to-point. This is in contrast to Wi-Fi devices, which typically need to be connected to a router first.
A hub for Zigbee or Z-Wave is still needed, but it's a few rooms away from the accessories, as long as there are enough compatible products interspersed in between to form a mesh. can do.
Many Thread accessories can act as their own “border routers”, providing a bridge to Wi-Fi and the Internet, often eliminating the need for a dedicated hub. Check the requirements for use on your chosen platform. For example, Apple HomeKit requires an Apple TV 4K or HomePod as a hub for all wireless protocols, but not all models support Thread.
If you have a good signal throughout your home, why not use Wi-Fi? First, most Wi-Fi-based devices require a pairing process that connects them to the manufacturer's servers. Aside from privacy and security implications, it can lead to fragmentation if you're not careful. Imagine half of his devices being controlled within his one app, and the rest residing within other walled ecosystems. Not very convenient, right?
This problem can be alleviated by limiting your accessory selection to one platform, such as Amazon Alexa, Google Home, Samsung SmartThings, or HomeKit. Still, Wi-Fi device automations are often triggered in the cloud and can stop working if you lose internet access. The Thread, Zigbee, and Z-Wave ecosystems can handle automation locally, and because the protocols are industry standards, a single hub/border router could potentially communicate with devices from many manufacturers.
Local processing also means immediate response and should not be underestimated. Turning smart home accessories on and off should feel like a switch, but the vast majority of Wi-Fi devices require relatively slow internet-based control, even if they're on the same network.
Thread, Zigbee, and Z-Wave allow automation to be processed locally, making it more reliable and faster.
Another advantage over Wi-Fi is lower power consumption. This keeps a Thread, Zigbee, or Z-Wave room sensor smaller than a room sensor with Wi-Fi (or Bluetooth), and can potentially operate for more than a year on battery power. Wi-Fi is sometimes so power-hungry that you have little choice but to use it from a power outlet.
Wi-Fi products may be cheaper, but resist the temptation unless there is an alternative for the functionality you are looking for. Thread, Zigbee, and Z-Wave tend to just work, and the peace of mind is worth the premium.
Be careful here – thanks to the October 2022 launch of the Matter networking protocol, platform compatibility issues may eventually become a non-issue. Matter-branded products work with all major smart home platforms, and many Matter devices will also support Thread sooner or later. We'll have to wait and see how long it takes for Matter over Thread to be widely adopted.
2. Smart speakers alone are not enough for true automation
Adam Molina / Android Authority
Marketing may tout that smart speakers like Google's Nest Audio are all you need to run a smart home, but they can be embarrassingly bad at actual automation.
Google Assistant routines cannot be processed or run locally, at least without a recently rolled out feature: Matter and Thread upgrades for existing devices. This means that if your internet connection fails, your nighttime lighting routine can also come to a halt. Voice commands are also processed in the cloud, which makes them completely non-functional.
Amazon's Echo lineup offers slightly better features in this regard. Devices like the 4th generation Echo and Echo Show 10 have their own Zigbee radios and can be used as suitable offline hubs. Amazon's automation routines are also a bit more sophisticated, although functionality is still limited compared to dedicated Zigbee hubs. Note that most Echo models (such as the Echo Dot) are limited to Wi-Fi automation. The 4th generation Echo is the only Amazon product to feature both Matter and Thread.
I still love my Google Nest smart speaker and display, but only as a remote control or multi-room audio system.
3. Choose your hub and sled devices carefully.
Edgar Cervantes / Android Authority
Now that you know why you need a hub-based or sled-based system when building a smart home, let's take a look at your current options. These are products that will be connected to everything in your home, so reliability and ease of use are paramount.
There are basically two types of hub devices and thread devices. One is fixed to the manufacturer and the other can be connected to almost any device. A gated ecosystem promises a curated user experience. However, this can lead to proprietary protocols, “certified” stickers, and/or unfair price premiums. More on this later.
Proprietary home automation ecosystems can be frustrating. Interoperability is important.
Anyway, what should you get if you're just starting out? Here are some options I recommend.
SmartThings: Samsung's SmartThings hub is easy and intuitive to use. It is compatible with a wide range of Zigbee and Z-Wave products, and also supports community-developed plug-ins for non-standard devices. Look for Aeotec hubs as an alternative. Home Assistant: Home Assistant is a very powerful and configurable platform, but unfortunately it's not very beginner-friendly. Thankfully, like most open source projects, there is a huge community that is constantly adding new features and devices. If you're a fellow tinkerer, there's nothing better than this. Please note that this is not a simple weekend project. Hubitat: Hubitat is one of the smaller companies in the smart home industry, but it combines the best aspects of SmartThings and Home Assistant. Simple, feature-rich, and locally controllable. Hubitat prides itself on customizability and great device support. HomeKit: As long as you can control it using your iPhone or iPad, Apple's platform is incredibly feature-rich and versatile. Apple TV and HomePod automatically become hubs. The drawback other than Apple's exclusivity is that by default it does not support Zigbee or Z-Wave. These protocols require a separate hub. Threads exist, but only if one of your Apple hub devices has them, as mentioned above.
4. A smart home doesn't have to be expensive
Assuming you choose Thread, Zigbee, or Z-Wave as your smart home protocol, there's no reason to stick to one brand or ecosystem. Both SmartThings and HomeKit have detailed lists of partner brands and compatible devices on their respective websites. Although Hubitat and Home Assistant do not offer certification due to their open nature, they work on more devices than you might expect.
Why is this important? Let's take a motion sensor as an example. If you own a SmartThings hub, you don't need to purchase Samsung's first-party option. A worthy alternative is Aeotec's Z-Wave multi-sensor, which combines temperature, humidity, movement, and even UV in his one package. Another option is the Enbrighten Z-Wave sensor, which bundles an in-wall light switch and instead draws power from the wall.
If you're feeling a little more adventurous, lesser-known options are also worth a look, such as Xiaomi's Aqara, eWeLink's Sonoff, and Ikea's Trådfri platform. In my experience, devices from these brands almost always give satisfactory results at a fraction of the cost.
Compatibility isn't always guaranteed, but a quick Google search or two can save you a lot of money.
Smart home products from IKEA and Xiaomi offer acceptable performance at surprisingly low prices.
There are some notable compatibility exceptions. For example, Philips Hue is very easy to set up, but it doesn't have a very open ecosystem. Many third-party Zigbee lights can be paired, but functionality is not guaranteed unless they are certified under the “Friends of Hue” program. Official Hue accessories, such as sensors, aren't cheap either. One reason is that there are few alternatives. Naturally, most Hue users I know have only bought his second hub for other devices.
5. You can’t trust the cloud – smart homes still require manual control
Calvin Wankhede / Android Authority
Once you have automation up and running, you may want to do away with light switches. After all, you don't want someone to turn off your smart lights or break your automation. Well, it's not that simple.
Unless you live alone, it's important that the smartness of your home be as discreet as possible. What works for you may not be the ideal choice for someone else. And the last thing you want is a family or guest who can't even turn on the lights. Trust me, I've been there.
Another thing to consider is that server outages are common, or at least common enough. Even big companies like Hue and LIFX tend to go offline from time to time. The more services that work together, the more likely these outages will impact you. Cloud-to-cloud connections like Google-Hue failed me many times, even though both platforms worked fine with their respective apps.
Try designing a smart home with offline functionality as a fallback.
Design automation systems with offline functionality in mind. Of course, this starts with choosing a hub or thread-based device that won't turn you into a paperweight in the absence of an internet connection. When it comes to manual lighting control, switches are still the norm. If you're concerned about the power consumption of your smart devices, a smart switch is the way to go. The automation will continue to run and you won't have to worry about manually restoring power.
Personally, I use a wireless, battery-powered Zigbee switch right next to the dumb switch. I admit that this is not the most beautiful solution, but you can also have a suitable solution within the wall. I highly recommend the Lutron and Inovelli switches, but be aware that they are quite expensive.
I hope my findings will help make your home automation journey a little easier. My final advice is to start small. Try limiting yourself to a few devices and sensors at first. You can always introduce hardware in stages depending on your needs.
This approach allows you to gain valuable real-world experience. Eventually, you may find that certain things aren't worth automating. Building a smart home and making it work is a marathon, not a sprint.
comment
Source link