You’d be forgiven for thinking this was going to be an anti-IoT rant: who the heck needs an IoT rice cooker anyway? [Microentropie], that’s who. His rice cooker, like many of the cheapo models, terminates heating by detecting a temperature around 104° C, when all the water has boiled off. But that means the bottom of the rice is already dried out and starting to get crispy. (We love the crust! But this hack is not for us. This hack is for [Microentropie].)
So [Microentropie] added some relays, a temperature sensor, and an ESP8266 to his rice cooker, creating the Rice Cooker 2.0, or something. He tried a few complicated schemes but was unwilling to modify any of the essential safety features of the cooker. In the end [Microentropie] went with a simple time-controlled cooking cycle, combined with a keep-warm mode and of course, notification of all of this through WiFi.
There’s a lot of code making this simple device work. For instance, [Microentropie] often forgets to press the safety reset button, so the ESP polls for it, and the web interface has a big red field to notify him of this. [Microentropie] added a password-protected login to the rice cooker as well. Still, it probably shouldn’t be put on the big wide Internet. The cooker also randomizes URLs for firmware updates, presumably to prevent guests in his house from flashing new firmware to his rice cooker. There are even custom time and date classes, because you know you don’t want your rice cooker using inferior code infrastructure.
In short, this is an exercise in scratching a ton of personal itches, and we applaud that. Next up is replacing the relays with SSRs so that the power can be controlled with more finesse, adding a water pump for further automation, and onboard data logging. Overkill, you say? What part of “WiFi-enabled rice cooker” did you not understand?
Looking at the plate on the bottom of his electric rice cooker, [AC_Hacker] was surprised to find that it was rated to consume 400 watts. Furthermore when he measured its consumption he found that it consumed 385 watts without even having a cooking cycle initiated. The circuit to keep cooked rice warm was always on – even when the cooking circuit wasn’t engaged.
Something clearly had to be done, so he set about modifying the cooker for better economy. Removing the base revealed that disabling the warming circuit was as simple as disconnecting it. [AC_Hacker] also noticed that the device had no thermal insulation. There was plenty of space between the inner and outer walls, so he packed it with glass wool. The final modification was to reduce the power taken by the heater by installing a half-wave rectifier diode. The cooker still reached the desired temperature, it just used half the power.
You might think that would be the end of it, given that the modifications significantly reduced the cooker’s power consumption without detriment to its rice cooking ability. Rice now took a little longer to cook, so there was still room for improvement. The moment of inspiration came when [AC_Hacker] realized that the cooking time was proportional to the amount of water used in a cooking cycle. He could safely reduce the water without affecting the cooked rice. A 30% water reduction led to a proportional cooking time reduction, and rice cooked using a lot less power.
Surprisingly this seems to have been Hackaday’s first rice cooker hack. Perhaps that’s because you’ve been so busy supplying us with sous vide hacks to write about.
[Craig] pulled off a beautiful build with his Sous Vader project. The name is a geeky spin on sous vide, a method of cooking foods in water held at a precise temperature. Building your own setup at home saves a ton of money, but it’s also a lot of fun. This explains the frequency with which we see these builds here at Hackaday.
So this one has a flashy name, a fine-looking case, but the beauty continues on the internals. [Craig] posted an image with the cover off of the control unit and it’s absolutely gorgeous inside. Part of the reason for this is the circuit board he spun for the project which hosts the ATmega328 and interfaces with the LCD, buttons, temperature sensor, and mains-switching triac. But most of the credit is due to his attention to detail. The image on the right shows him prototyping the hardware. Since some of his meals take 20 hours to prepare it’s no wonder he found an out-of-the-way closet in which to do the testing.
Make sure to read all the way to the bottom of the post for some cooking tips. For instance, since he doesn’t have a vacuum sealer he uses zipper bags — lowering them into water to push out the air as they are sealed.