Your lock speaks Bluetooth, the bulbs want Wi‑Fi, the thermostat has its own cloud. Each app nags about firmware. A hub promises one dashboard; it also adds another box that can fail on update night.
Standalone apps shine when you own three devices and hate tinkering. Onboarding is direct; features match the manual. Scaling to fifteen gadgets without scenes or automations turns phone swiping into a part-time job.
Hub vs. separate control
| Topic | Central hub platform | Per-device apps |
|---|---|---|
| Initial setup | Steeper; pays off with rules | Fast for one gadget |
| Guest access | Shared scenes, limited roles | Share accounts or passcodes ad hoc |
| Vendor shutdown | Hub obsolescence risk | Device may still work locally |
| Local control | Varies; some hubs cloud-heavy | Often cloud-only for cheap gear |
| Privacy review | One vendor to read | Many policies to track |
Standards slowly converge—Matter and Thread reduce some friction—but shelves still mix generations. Check compatibility lists before Black Friday enthusiasm.
Automations are the real product. “Lights off when everyone leaves” beats a pretty tile grid. Hubs express logic; apps often stop at remote toggle.
Outages teach humility. Cloud-down means no doorbell video even if power works. Prefer devices with local fallbacks for locks and heat where safety matters.
Label circuits and bulbs in app names—“kitchen counter,” not “bulb 4.” Future you will not remember which is which at 11 p.m.
Guest networks isolate cheap IoT from laptops holding taxes. Router guest SSID is free segmentation if you use it.
Buy for the job: renter with two lamps needs apps; homeowner wiring scenes for years may earn a hub. Neither choice is virtue—match complexity to tolerance for maintenance.
