Data specialist Mark Rittman wanted to make tea around 9:00AM, but found himself in an eleven hour saga trying to get his wi-fi tea kettle to work. He documented his struggle on a website that’s also struggling, a social network called Twitter.com.
https://twitter.com/embed/status/785751015517814784
While Rittman did acquiesce to boiling his water the old-fashioned way—in a “saucepan”—his struggle with his wi-fi kettle continued well into the day.
3 hrs later and still no tea. Mandatory recalibration caused wifi base-station reset, now port-scanning network to find where kettle is now. pic.twitter.com/TRQLuLzLpx
— Mark Rittman (@markrittman) October 11, 2016
Now the Hadoop cluster in garage is going nuts due to RT to @internetofshit, saturating network + blocking MQTT integration with Amazon Echo pic.twitter.com/ryd42c5ewj
— Mark Rittman (@markrittman) October 11, 2016
Now my wifi kettle is basically taking the p*ss. Told me it had found network, now you need to recalibrate me, oh btw I didn't rly connect pic.twitter.com/WbGsIrzBio
— Mark Rittman (@markrittman) October 11, 2016
Rittman literally had to hack his kettle in order for the water to get boiled… 11 hours later.
Well the kettle is back online and responding to voice control, but now we're eating dinner in dark while lights download a firmware update pic.twitter.com/yPTDoUkM9Z
— Mark Rittman (@markrittman) October 11, 2016
My work is done. And now onto everything else I meant to do today, after that first cup of tea. pic.twitter.com/bJPuJ85TCT
— Mark Rittman (@markrittman) October 11, 2016
What’s the lesson here? Never give up. JK, the lesson is fuck the internet of things. Go analog, baby.
