Devices Smart home and connected devices
Smart home basics: what to buy first and what to skip
How smart home devices actually connect, which categories are genuinely useful, and the decisions that stop you from owning five apps that do not talk to each other.
The short answer
- Choose one ecosystem before you buy any device, because that decision determines what will work together later.
- Sensors and lighting deliver the most for the least, while connected appliances tie a short software life to a long lived object.
- Wifi devices need no hub but drain batteries, while Zigbee, Z-Wave and Thread run for a year on a cell and need a hub or border router.
- Matter is a shared language rather than a radio, and it covers basic functions reliably while advanced features often still need the maker's own app.
- Most setup failures come from the device supporting only 2.4 GHz wifi while your phone is on 5 GHz.
- Prefer devices that still work when the internet is down, because cloud only products stop working when the company stops paying for servers.
Start with lighting and sensors, pick one ecosystem before you buy anything, and skip any device whose only trick is being controlled by an app. Order matters more than shopping. Most people who end up with a drawer of abandoned gadgets and five apps that ignore each other made a sequencing mistake: they bought a device they liked, then a second one that could not talk to it, and every purchase after that was a compromise. Decide how things connect first and the rest gets much smaller.
How smart devices actually connect
There are three patterns, and knowing which one you are buying explains almost every frustration that follows.
Direct wifi. The device joins your home network like a laptop and talks to the maker's servers. No hub needed, which is why these are easiest to sell. The cost is that wifi is power hungry, so this suits mains powered things like plugs and cameras rather than battery sensors, and every device is one more thing needing a password and updates.
A low power radio with a hub. Zigbee, Z-Wave and Thread are short range protocols designed for tiny messages and long battery life. A door sensor on a coin cell can run a year or more, which wifi could never do. They need something to translate between that radio and your network: a hub, or a border router built into a speaker or TV box. Mains powered devices on these networks relay for their neighbors, so coverage improves as you add more.
Bluetooth. Short range and paired to a phone. Fine for a padlock you stand next to, weak as the backbone of a house, because control stops when you leave the room.
Then there is Matter, which gets confused with all of the above. Matter is not a radio. It is a shared language that runs over wifi, ethernet and Thread, so a device can be controlled by more than one company's app. In practice support is uneven: basic functions like on, off, brightness and temperature travel well between systems, while the specialized features a device is proud of often still need the maker's own app. Treat Matter as insurance that the basics keep working, not a promise that everything will.
The ecosystem matters more than the gadget
The ecosystem is whichever assistant and app you run everything through. It decides which devices appear in one place, which automations are possible, and how much of your setup survives replacing a product. Choosing one and sticking to it is the highest value decision in a smart home, and it is free.
Judge candidates on four things rather than brand loyalty. Does it support the devices you own or intend to buy? Does it run automations locally, or does every light switch need a round trip to a data center? Does it work with the phones everyone in the house uses? And can you get your setup out again?
The lock in is subtle. It is rarely the device that traps you, it is the automations, room layout, names and voice routines built over two years. Rebuilding those is the real cost of switching, which is why the decision belongs at the start. If a voice assistant is going to be the front end, it is worth understanding first what that microphone does with what it hears, and what a smart speaker actually records and stores is the better article to read before you buy one.
Which categories earn their place
Usefulness follows one rule: the best devices remove a repeated action or tell you something you could not otherwise know. The worst add a step between you and a switch.
| Category | What it genuinely buys you | Where it disappoints |
|---|---|---|
| Lighting | Schedules, gradual wake and evening dimming, one command for a whole room, lights that respond to motion | Smart bulbs behind a wall switch stop working when someone flips it off |
| Sensors: door, motion, temperature, water leak | Information you had no way to get, and the trigger for every useful automation. A leak sensor under a washing machine can save a floor | Nothing, apart from the batteries you will forget about |
| Smart plugs | Turning dumb appliances into scheduled ones, plus energy measurement on the models that offer it | Useless for anything with a soft touch power button that does not resume when power returns |
| Heating and cooling control | Real savings from heating rooms only when occupied, and remote control when plans change | The savings depend on your habits and your building, not on the device |
| Cameras and doorbells | Knowing who called, and evidence when something happens | Ongoing subscriptions, and the privacy questions that come with a permanent recording |
| Locks | Keyless entry, temporary access for visitors, and a log of who came in | Battery failure and lockout planning become your responsibility |
| Speakers and displays | Hands free control, timers, intercom between rooms | An always on microphone in a room you may not want one in |
| Connected appliances | A notification when the wash is done | Software support that ends long before an appliance designed for fifteen years does |
The pattern is clear. Sensors and lighting sit near the top because they enable automation. Appliances and novelties sit at the bottom because they attach a short software life to a long lived object. A handful of sensors and a way to act on them will do more than any single expensive device.
The 2.4 GHz problem everyone hits
Almost every new owner hits the same wall: the app cannot find the device, or pairing fails near the end. This is usually not a fault. Most smart home devices support only the 2.4 GHz wifi band, because it travels further through walls and uses less power, while your phone is probably on 5 GHz. Many routers present both bands under one network name and choose for you, and during setup that choice goes the wrong way.
The fixes, from least disruptive: put your phone on the 2.4 GHz network if the bands have separate names, or split the combined network into two names during setup, or disable 5 GHz for five minutes while the device joins. Once connected it stays on 2.4 GHz and you can put everything back. Keep the device near the router while pairing, and check that guest network isolation is not blocking it. If none of the band names mean anything yet, the difference between 2.4, 5 and 6 GHz takes five minutes and will save you an hour.
Two related traps. A house with a dozen wifi gadgets can hit the device limit on a cheap router, which shows up as random dropouts rather than an error. And a device that pairs fine next to the router may fail where you install it, which is a coverage problem, so the choice between a mesh, an extender and a cable is worth settling before you blame the gadget.
What happens when the service is switched off
This is the part nobody mentions at the point of sale. Many devices are thin clients for a company's servers: press the button, the command travels to a data center, and the data center tells the device what to do. When the company is sold or shuts the service down, those devices can stop working while the hardware is still perfectly good. It has happened to hubs, cameras, speakers and lights.
The protection is local control: the device can be operated by something inside your home without the internet. Three tests before buying. Does it still respond with the broadband down? Does it use an open standard like Zigbee, Z-Wave, Thread or Matter rather than only a proprietary cloud? Does the maker publish a support period, the way phone makers now do?
Local control has a second benefit you feel daily: a light that responds instantly rather than after a visible pause. For anyone willing to run one extra box, community built home automation software can control devices from several brands and keep working after a vendor disappears, one of the clearest cases where open source software is worth the setup for a non developer.
The setup worth doing first
An hour at the start prevents most of the annoyances later.
- Pick your ecosystem, then check every purchase against it before ordering, not after.
- Give each service its own generated password, stored in a password manager. Reused credentials are how strangers end up inside other people's home systems, and why reusing one password is so expensive applies to a camera account more than almost anything.
- Turn on two step verification for the ecosystem account, since that one login controls everything else.
- Name devices and rooms carefully and consistently on day one. Renaming later breaks automations and voice commands.
- Put the gadgets on a guest or separate network where your router supports it, so a compromised plug cannot see your laptop.
- Enable automatic firmware updates everywhere they exist. These devices are the ones nobody patches, and which updates to install immediately and which can wait explains why firmware is the category that stays exposed for years.
- Write down where the batteries are and what size they take, then set one calendar reminder a year.
Then buy in order: two or three sensors, one lighting change that removes a daily action, and nothing else for a month. The second purchase will be far better informed than the first. If it is a camera, settle placement and access before it goes up, because keeping a camera feed away from everybody else is easier at installation than afterward.
Common questions
Do I need a smart home hub?
Only if you want battery powered sensors or local control. Wifi devices work without one, which is why starter kits avoid hubs. But battery sensors use low power radios that your router cannot hear, so something has to translate. That job is increasingly built into a speaker, TV box or newer router, so you may already own a hub without calling it one.
What is the difference between Matter and Thread?
Thread is the radio that carries the messages, and Matter is the language written in them. A Thread device needs a border router in the house to reach your network. Matter can also run over ordinary wifi and ethernet, so a Matter device is not necessarily a Thread device. Supporting both means it should appear in more than one company's app.
Why will my smart plug not connect to wifi?
Almost always because it only supports the 2.4 GHz band while your phone is connected to 5 GHz. Put the phone on the 2.4 GHz network during setup, or temporarily split a combined network into two names. Keep the device close to the router while pairing, and make sure client isolation on a guest network is not blocking it.
What happens to my devices if the company goes out of business?
It depends entirely on whether the device needs their servers. Anything that sends every command through a data center can become unusable overnight, while devices using Zigbee, Z-Wave, Thread or Matter can usually be adopted by another hub. Before buying, unplug the test: ask whether the thing still responds with the broadband down.
Are smart home devices a security risk?
The devices themselves are rarely broken into directly. The common failures are a reused password on the account that controls them, a shared login nobody revoked, and firmware that was never updated. Give each service its own generated password, turn on two step verification, and keep the gadgets on a separate network from your computers.