Is IoT a bubble?

Is IoT a bubble?

Judge connectivity by the problem it solves

IoT is not usefully dismissed as one big bubble, but individual products and projects can certainly be overhyped. The Internet of Things connects physical devices with systems that use their data. A failed product does not invalidate that approach. Equally, working IoT technology does not establish that every connected appliance is necessary or every deployment pays its way.

When “bubble” means marketing hype, compare the advertised outcome with demonstrated value. A financial investment bubble is a different claim, requiring evidence about valuations and revenue. A growing device count is not, by itself, proof that customers are receiving a worthwhile benefit.

Useful deployments have a clear purpose

Detecting a temperature excursion in a remote store, reporting a water leak or collecting meter readings across several sites can meet a practical need in everyday and business use. The value comes from earlier information, fewer unnecessary site visits or better visibility of losses. Collecting readings for a dashboard that nobody uses does not produce the same result.

In Industrial IoT (IIoT), motor current, runtime and temperature trends can support maintenance decisions. One measurement is not a definitive fault diagnosis: operating conditions and maintenance records matter too. Where existing SCADA and automation already meet the need, an additional cloud layer needs its own justification.

Recognize claims that need evidence

“The same savings everywhere”, “no more failures” and “install it and it pays for itself” leave important conditions unexplained. For energy savings, establish baseline consumption, the operating change and the electricity used by the control system itself. A polished app cannot substitute for that comparison.

Interoperability is more than connecting two products to Wi-Fi. Data formats, communication methods and permissions must align. Difficulty moving records to another supplier, or repeated charges for connecting additional equipment, can increase long-term ownership costs. The integration work missing from a sales presentation is still real project work.

Ask what survives the end of a service

This is a concrete product-lifecycle issue. Google’s support documentation records that Nest Secure support ended on April 8, 2024. Users relying on Nest Guard to bridge their Nest × Yale Lock to Wi-Fi needed Nest Connect instead. That does not describe every IoT product, but it demonstrates how device functionality can depend on a manufacturer’s continuing services.

Check support and update commitments, functions retained without a subscription, data export and behaviour during an internet outage. Local processing and control can improve resilience in some architectures. AWS IoT Greengrass documentation, for example, describes a configuration allowing local clients to authenticate and connect while the core device is disconnected from the cloud. This requires appropriate setup; it does not mean every product works offline or that cloud access is never needed.

Security questions deserve technical answers

Questioning device security, data-breach exposure and privacy is a sensible part of evaluation. NIST IR 8259A discusses foundational capabilities covering identification, configuration, data protection, interface access, software updates and reporting cybersecurity state. Assessing those capabilities does not guarantee complete security, but it provides a concrete starting point for choosing equipment.

Establish what data is collected, why it is needed, who can access it and how long it remains stored. Continuous monitoring is not essential for every application. Security for always-connected devices also needs attention throughout their operating life, rather than only at purchase.

Evaluate outcomes rather than labels

A useful technology and a poor product can coexist. Measurement quality, usability, maintenance effort and actual results determine whether a deployment is worthwhile. Unnecessary replacement of working hardware can create electronic waste, while changes to jobs and tasks deserve consideration alongside technical benefits. Discussions of IoT’s future are more informative when they distinguish demonstrated outcomes from promises, rather than assuming that every project will succeed or that none can.

References

NIST IR 8259A: IoT Device Cybersecurity Capability Core Baseline
Google: Nest Secure support and Nest × Yale Lock connectivity
AWS IoT Greengrass: Authenticating clients while offline