Why This Matters
A hobbyist's teardown-by-network-scan of a cheap Lidl WiFi kettle is a small but telling window into how consumer IoT actually works: the device doesn't expose a friendly local API, it pairs via its own open access point and then talks over a single obscure port (TCP 6668) with no banner, implying a proprietary cloud-linked protocol. For consumers, it shows that 'smart' appliances often can't be controlled locally without reverse engineering; for the industry, it highlights the ongoing tension between vendor lock-in and the hacker/home-automation community.
Key Takeaways
- The kettle sets up via its own open, DHCP-less access point and a vendor app that hands over WiFi credentials.
- Network scanning revealed only TCP 6668 open, with no banner or web interface — a proprietary, non-HTTP protocol rather than an open local API.
- App functionality is limited (temperature presets, keep-warm, no scheduling), motivating enthusiasts to probe for local control.
Last saturday while grocerie shopping I saw a wifi controlled "Smart Kettle" in the special offers isle. This reminded me of the as april fools joke written HTTP status code 418 "I'm a tea pot" and posted jokingly this toot on mastodon.
Well the itch got worse and so I finally bought one of these high tech devices to boil some water.
Since I had not yet done any projects or hacking on smart wifi IoT devices ,I had no idea how it works and what I had to expect. My first thought was, the smartphone app talks directly to the smart kettle, on which runs some kind of server / api one could talk to.
First things first, I hooked up the kettles base to mains power and pushed the wifi button on it. It beeped, flashed and who would have guessed, it spawned it's own open access point. ;)
... continue reading
GoKawiil