The Internet of Things: How Smart Devices Connect Our World

How smart devices actually connect to the Internet of Things

Your doorbell knows you're not home. Your thermostat has already decided the living room should be 19°C when you walk in. And somewhere in a factory you'll never visit, a vibration sensor just flagged a bearing that will fail in three weeks. None of these devices talk to each other directly. They all report to something.

That "something" is the Internet of Things, and the word Internet is doing more work in that phrase than most people realise. The interesting part isn't the gadgets. It's the plumbing.

I've been building small connected systems for a while now — a handful of sensors in a garage, a meter-reading setup for a local business, a zigbee mesh in my own flat that I rebuilt twice before it stopped dropping devices. What follows is what I actually learned about how this stuff connects, plus the parts that genuinely don't work the way the brochures suggest.

What are smart devices and how do they contribute to the Internet of Things?

A smart device is any physical object with three additions: a sensor or actuator, a small computer, and a way to send what it measures somewhere else. That's the whole definition. A dumb thermometer measures temperature; a smart one measures it, timestamps it, and ships the reading over a network.

Contribution is where people get it wrong. A single smart bulb contributes almost nothing. Ten thousand of them, reporting power draw across a city grid, let an operator spot a substation straining before it trips. The value is in the aggregate, not the object.

What does IoT stand for, and who came up with it?

IoT is short for Internet of Things. The term is usually credited to Kevin Ashton, a British technology researcher who used it in a presentation in 1999 while working on supply-chain tagging with RFID chips. His original framing had nothing to do with consumer gadgets — it was about making physical goods self-identifying so computers could track them without a human typing anything in.

That origin still explains the field better than most modern descriptions. RFID, barcodes, inventory: the first IoT was logistics.

How does the Internet of Things actually work?

Four steps, repeated millions of times a second.

1. Sense. A sensor samples something — temperature, movement, current, position, vibration.
2. Process locally. A microcontroller decides whether the reading is worth sending. Good designs filter aggressively here; bad ones transmit everything.
3. Transmit. The device sends a small packet to a gateway, hub or cloud broker over some radio protocol.
4. Act or store. A rule fires, a dashboard updates, a technician gets an alert, or the data just accumulates for later analysis.

Step two is the one beginners skip, and it's the one that decides whether your battery lasts five years or five weeks. I learned this the hard way: my first outdoor sensor pushed a reading every ten seconds and ate a lithium cell in eleven days. Same hardware, changed to a five-minute interval with a threshold filter, ran for over two years.

Which connection protocols do smart devices use?

This is the technical heart of the subject, and it's usually missing from explanations. Devices don't just "connect to the internet." They pick a radio technology matched to range, power and bandwidth.

Protocol	Typical range	Power profile	Best suited to
Wi-Fi	~30 m indoors	High drain	Mains-powered cameras, speakers, TVs
Bluetooth LE	~10 m	Very low	Wearables, locks, trackers paired to a phone
Zigbee / Thread	~10–20 m per hop, mesh	Low	Bulbs, sensors, switches in a home or office
LoRaWAN	2–15 km rural	Extremely low	Water meters, soil sensors, agriculture
MQTT (over any IP link)	Wherever the network reaches	Depends on bearer	Software layer: how messages travel to a broker

Two clarifications that saved me a lot of confusion. MQTT isn't a radio — it's a messaging pattern (publish/subscribe) that runs on top of Wi-Fi, Ethernet or cellular. And Zigbee and LoRaWAN are radios, not messaging systems, though you still need something above them to route data sensibly.

Sensor full form, since it comes up constantly: the word is just "sensor," from the Latin sentire, to perceive. There's no acronym hiding in it, unlike IoT or IIoT (Industrial Internet of Things).

How is the Internet of Things being used in smart cities?

Forget the renderings with glass towers and floating holograms. Real smart-city deployments are almost aggressively boring, and that's the point.

The most common application by a wide margin is adaptive street lighting. Lampposts fitted with motion and ambient-light sensors dim to 20–30% when nobody's around and brighten when a pedestrian or vehicle approaches. Cities that have rolled this out report electricity savings in the range of 30–50% on lighting alone — and lighting is typically one of the largest single line items in a municipal energy budget.

Second: waste collection. Fill-level sensors in public bins mean trucks empty the ones that are full instead of driving a fixed route past half-empty containers. Operators running these systems commonly report cutting collection trips by a third or more.

Third, and the one I find genuinely useful as a resident: traffic. Inductive loops and camera-based counters feed signal timing that adjusts in real time rather than running a fixed cycle written in the 1990s.

Which cities have done this at scale?

Barcelona is the example most people cite, and it earns it — sensor networks across irrigation, parking and lighting, with irrigation alone cutting water use substantially in public parks. Amsterdam ran a long-standing open-data programme that let residents build their own applications on top of municipal sensor feeds, which is a rarer and more interesting model than the top-down version.

Singapore went further on the infrastructure side, deploying sensor networks for everything from drain monitoring to elderly-care alerts in public housing. The honest assessment: some of these projects delivered, some quietly faded after the pilot funding ran out. That's normal and rarely reported.

The pattern that separates successes from failures isn't technology. It's whether a city has someone whose actual job is maintaining the network after launch. Sensors need batteries, firmware and replacement. Most pilot failures I've read about were maintenance failures wearing a technology costume.

How many devices are connected to the Internet of Things?

Current estimates put the global installed base somewhere in the region of 17 to 20 billion connected devices, with most industry forecasts projecting that figure roughly doubling by the early-to-mid 2030s. A frequently cited projection lands above 40 billion devices by 2034.

Treat those numbers with a specific kind of caution. Nobody counts this directly. Analysts extrapolate from chip shipments, module sales and operator reports, which means the totals move by billions depending on methodology. I've seen the same year reported as 14 billion and 18 billion by two different firms, both confident.

What's more useful than the headline figure is the composition. The overwhelming majority of connected devices are not consumer gadgets. They're industrial sensors, utility meters, fleet trackers, agricultural monitors and building-management systems. If you stripped every smart speaker and fitness band off the network, the total wouldn't drop by much.

And the growth rate is lumpier than the smooth exponential curves suggest. Consumer IoT saturated fast in wealthy markets — most households that wanted a smart thermostat have one. Industrial adoption is slower because retrofitting a factory floor is expensive and the payback period is measured in years, not quarters.

Which devices should you actually connect to your network?

Here's my genuinely opinionated answer, and I'll defend it: connect fewer things than you think you need, and prefer devices that keep working when the internet doesn't.

That second criterion eliminates a shocking amount of the market. Plenty of inexpensive smart plugs and bulbs are useless without a cloud connection — the app talks to a server, the server talks to the device. Router goes down, lights stop responding to the wall switch. I've thrown out hardware over this.

A practical shortlist

• Worth it: smart thermostat, leak sensors, a couple of smart plugs on high-draw appliances you want to monitor, and a hub that speaks Zigbee or Thread locally.
• Situationally worth it: cameras (only if you've thought through where the footage is stored), smart locks with a physical key backup, lighting in rooms you actually use.
• Rarely worth it: connected refrigerators, washing machines with apps, anything whose "smart" feature is a notification you'll mute within a week.
• The one rule that matters: if the device can't perform its core function without a working internet connection, ask yourself what you'll do when that connection or that company disappears.

I'll admit I got this backwards at first. My early setup was fifteen devices, four apps, three bridges and constant friction. Now it's a hub, six devices, one app, and it has run without intervention for well over a year. Fewer things, better chosen.

Where this leaves you

The Internet of Things isn't a single network. It's thousands of overlapping ones, speaking incompatible dialects, glued together by gateways and brokers that somebody has to maintain. The magic isn't that your bulb turns on from your phone. It's that a water utility can find a leak in a pipe under a road nobody has dug up in forty years — because a sensor the size of a coin has been whispering a number to a receiver every six hours for a decade.

That's the version worth paying attention to. The consumer gadgets are a side effect.

One question worth sitting with: the next time you buy something with "smart" on the box, ask what happens to it in five years when the company that made it has moved on. Your answer will tell you more about the actual state of connected devices than any device count ever will.