It's been pretty hot lately, and I decided I needed a fan in my study, and moreover I wanted a smart fan so I could control the use of the fan versus the air purifier automatically based on the temperature and whether the window is open. Initially I was open to a fan with a remote control, which I could control via an infrared blaster (albeit without feedback or live state), but what I really wanted was one with Zigbee or Wifi but not dependent on a cloud service.

Friends: this morning while I was performing my ablutions, my kettle turned on - and by the time I reached the kitchen, there was boiling water ready for my coffee. How did I get here? Of all my projects that get sidelined and take forever to complete, is 13 years a record? Why can't I stop grinning from ear to ear even with no-one else around?

In part one of Kettle Quest, I explained my reasons for wanting kettle automation and some of the early solutions I had explored to reach my goal. In part two I found an off-the-shelf product in Weekett that promised me a ready-made solution, but turned out to be a huge disappointment that has defrauded thousands of consumers by turning their smart kettles dumb.

In part one of Kettle Quest, I explained why I wanted a smart kettle and shared my disjointed journey trying to make a dumb kettle smart. After years of compromises and half-solutions, in 2024 I finally found a kettle marketed as being inherently smart and connected out of the box.

It's a momentous day for me here, as I think a 13-year quest is finally at an end, and soon I won't be waiting for the kettle to boil every morning, or turning it on with a finger like a pleb. But this has been a long, long quest, so please indulge me for part 1, where I reflect for a moment on my journey to get here.

After a four-year enforced pandemic-based hiatus, we were back for our latest installment of EMF in June with nearly 2,750 people on site. Back at Eastnor Castle deer park again this year, we were able to use the street cabinet and fibre around the field that we installed in 2018 to get up and running quickly once we arrived on site.

In a world where FTP has finally been turned off by most ISPs, Wordpress allegedly supports SSH2 for upgrades instead, using FS_METHOD ssh2. However it fails to work in any real-world scenario because it assumes the filesystem paths on the remote host are the same as on the local filesystem.

This obviously fails with pretty much any ISP on earth as the users are chroot()ed, so a directory that was once perhaps /home/david/www.davidc.net would in fact be just /www.davidc.net when accessed over SFTP.