This is why you don’t want a Wi-Fi kettle
A disclaimer before I begin: I don’t do hot drinks. As such, I’m not really sure how long it should take a kettle to boil enough water for a cup of tea. All I can say with any real confidence is that it definitely shouldn’t take 11 hours.
Unfortunately, that was the experience of data specialist Mark Rittman, who spent the majority of his Tuesday getting his new Wi-Fi kettle to do what regular electric kettles have been doing since 1891. Boiling water.
Three hours later. Still no tea.
Forty-five minutes later, and his ongoing kettle problems were becoming a viral sensation. Unfortunately, this newfound attention was really hampering his progress as his new kettle still resolutely refused to play ball.
I think at this point I’d have given up and drank some cold water, to be honest.
It should be said that your average tea enthusiast shouldn’t have this much trouble with the kettle. Some of the problem can be attributed to the fact that Rittman was attempting to add in his own DIY connected home functionality, to allow the kettle to chat freely to his Amazon Echo.
Eleven hours after setting off on his journey, Rittman’s Twitter followers were finally seeing an end in sight for this rollercoaster adventure.
And there it is, at ten past midnight, the kettle was ready to make its debut cup of tea.
Welcome to the future. I’d keep your old kettle, just in case, if I were you.
Image: Bradley Higgenson, used under Creative Commons