Every June, the tech press loses its mind over Prime Day. Discounted Echos, Ring cameras, Fire TVs, smart plugs. You can save up to $320 on household gadgets, apparently. Good for you if you need a new speaker.
But here's the thing: I keep seeing this stuff lumped in with "automation" and "smart technology" in the same breath as actual industrial systems, and it's starting to grate on me.
When I was at Kuka, we spent months getting a single cell to communicate reliably with a PLC over PROFINET. We're talking about deterministic timing, safety-rated I/O, SIL 2 compliance. The kind of work where a misconfigured parameter doesn't just mean your living room light doesn't turn on. It means a 200-kilogram arm swings somewhere it shouldn't.
A smart speaker that plays Spotify is not in the same category. I'm not being snobbish about it. Both things can be useful. But the word "smart" has been so thoroughly stretched that it now covers everything from a $29 Echo Dot to a fully integrated SCADA system, and that conflation does real damage to how people understand the field.
The CNET Smart Home coverage of Prime Day 2026 is perfectly competent consumer journalism. Fifty-plus deals on Amazon devices, TVs, security cameras. Fine. That's what it is. What it isn't is robotics or industrial automation, and I'd gently push back on any outlet that frames it that way.
This is, in a way, a vocabulary problem more than anything else. The industry I came up in had fairly precise language. A robot was a reprogrammable multi-axis manipulator. Automation meant removing a human from a repetitive or hazardous task through engineered systems. "Smart" meant something specific about adaptive control or sensor feedback.
Now "smart home" is a product category that includes a security camera you check from your phone. That's basically a webcam with an app. I'm not saying it's worthless. I'm saying the terminology drift makes it harder for people entering the industry to understand where the real engineering complexity lives.
I called my old colleague Dave, who spent years doing systems integration for automotive lines, and he made the same point last month. His frustration was that younger engineers sometimes arrive expecting warehouse automation to feel like setting up an Alexa routine. It doesn't. It never will. The physics don't care about your user experience.
There's a practical consequence here that I think gets underappreciated. When consumers spend years interacting with "smart" devices that are genuinely easy to set up and use, their expectations for industrial systems shift accordingly. And then procurement teams start asking why a robot integration takes eighteen months and costs seven figures when their Ring doorbell took twenty minutes and cost $99.
The answer, obviously, is that the problems are completely different. Reliability requirements are different. Safety requirements are different. The consequences of failure are different. A Ring camera going offline means you missed a porch delivery. A conveyor system going offline in a fulfilment centre means you've got a problem that cascades through the entire operation within minutes.
It remains unclear whether this expectation gap is actually getting worse or whether I'm just noticing it more as I get older. Probably some of both. But the blurring of language between consumer tech and industrial systems doesn't help.
Look, I'm not suggesting CNET should stop covering Prime Day deals. That's their audience and their job. And honestly, some of the home automation stuff, the better Zigbee-based systems, the more serious home energy management platforms, those do share genuine engineering DNA with industrial controls. The line isn't perfectly clean.
But a $29 Echo on sale is not a data point in the story of where robotics is going. It's a consumer electronics discount. Let's just be clear about which conversation we're having.