
If you were to ask American’s to describe Britain in as few words as possible chances are that as well as the Queen, tea-drinking would rank pretty high in their answers too.
And this story just proves how much we all love a good ol’ cuppa, according to Mashable.
Do you remember that episode of Father Ted where Ted buys Misses Doyle a TeaMaster that she absolutely despises because it’s too techy. Well now even for me things have too techy with the recently released WiFi kettle…
And like all things techy, they fuck up – a lot as one incredibly unfortunate data specialist, Mark Rittman, found out last week when trying to make a lovely brew with his Wi-Fi kettle.
Fortunately, Mark tweeted the entire thing. From his optimistic and thirsty beginning to the 11 hour soul-destroying struggle which followed.
He began by tweeting: ‘Still haven’t had a first cup of tea this morning, debugging the kettle and now iWifi base-station has reset’.
Yep, I have no idea what that means either.
He continued:
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 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
As you can probably imagine, plenty of helpful Twitter users were on hand to offer Mark some great advice:
why don't you just get normal fucking kettle
— ? kade ? (@onekade) October 11, 2016
30 seconds sorted ? https://t.co/BAYwNPkMcE
— Little Spacey (@daviek28) October 17, 2016
.@markrittman Just get a teasmade, it has the advantage of not being connected to the internet https://t.co/6RD2Wuepa8
— Neil Boothman (@neilboothman) October 13, 2016
Mark wasn’t discouraged:
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
It is, and OK apart from flaky WiFi connectivity; main issue is that there's no IFTTT or HomeKit integration, so hacked that together myself https://t.co/0IjD7q4wzM
— Mark Rittman (@markrittman) October 11, 2016
Because it doesn't come with IFTTT support, so I used netcat + Python script that IFTTT Maker channel calls via HTTP GET
— Mark Rittman (@markrittman) October 11, 2016
And finally – after 11 hours of incessant struggling Mark finally conquered this beastial machine and boiled water:
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
They say that good things come to those that wait, but personally I think I’ll stick to my normal kettle.
