You've heard the hype: The Internet of Things (IoT) will transform the way we live and work, bring us untold benefits like cutting our utility bills and warning us when the milk has gone sour, and be the engine for the next great economic boom. McKinsey claims, for example, that the IoT could have an impact of $11.1 trillion per year by 2025 -- about 11% of the world economy, by McKinsey's estimate.
I'm not an economist, so I can't comment on McKinsey's estimates. But based on my recent experiences with Internet access built into a variety of "things" in my house, the IoT could become our worst personal IT nightmare.
My problems started with an all-too-common occurrence: My Wi-Fi router burned out and I had to replace it. This happens regularly enough that I keep another router as backup. I turned it on, then connected it to my cable modem and Sonos bridge for wireless music streaming. I was feeling smug -- I used the same SSID and password as the previous one, figuring that all the devices would automatically connect to it.
Ah, if life in the IoT age were only so simple.
My first problem was with my Samsung smart TV, which didn't prove to be particularly smart. I tried Netflix on it. No go. Amazon Prime. It didn't work. Hulu Plus. Nothing. The TV wasn't smart enough to connect to the new network, even though its settings were identical to the old one. After 45 minutes of getting lost in a maze of incomprehensible menus and settings, I finally stumbled onto a screen that let me log into the new network, using the exact same SSID and password that was already in the TV.
Next up, my Sonos bridge and six wireless Sonos speakers. None of them recognized the new network. After four tries of attempting to connect, the bridge worked. Then I started in on the first speaker. I followed Sonos' instructions more than 10 times. No connection. I moved onto the second. After 10 times it didn't work, either. After an hour of trying each speaker in the house, I gave up. Then I noticed that one of the speakers, seemingly on its own, made the connection. But no others did. After two days of trying, all the speakers eventually connected, although I'm not quite sure how and why.
My work still wasn't done. My Lexmark E120n networked laser printer wouldn't work. This was the most baffling of all, because it was designed to work on a network.
I restarted the printer, assuming that my router would assign it a new IP address. Nope. I figured that downloading a new driver or Lexmark software would fix the problem. But Lexmark's support page for it was down. I managed to find the driver elsewhere and installed it. That didn't solve the problem. I eventually found a Lexmark IP configuration utility that should have worked but didn't. The printer still had the IP address the old network had given it, and that address didn't work on the new network. I did a factory reset, but that didn't reset the IP address. I tried telnetting into the printer to run a setup utility built into the printer's firmware. But, of course, because the printer wasn't on the network, I couldn't telnet in.
Sign up for Computerworld eNewsletters.