92 lines
4.2 KiB
Markdown
92 lines
4.2 KiB
Markdown
---
|
|
title: "Smart Rice Cooker Conversion"
|
|
date: "2018-06-18"
|
|
author: "William Floyd"
|
|
categories: [
|
|
"Development",
|
|
"Hardware",
|
|
"Software"
|
|
]
|
|
tags: [
|
|
"Arduino",
|
|
"Rice Cooker",
|
|
"Aliexpress"
|
|
]
|
|
---
|
|
|
|
The "why" isn't important (read "doesn't exist"), but I want to take a regular old "dumb" rice cooker, and convert it into a "smart" rice cooker.
|
|
|
|
So, a whim and a few minutes on Aliexpress later, my pint sized rice cooker and an assortment of electronics are on the slow boat from China.
|
|
|
|
Having no real clue what I'm doing, here's what I've ordered thus far:
|
|
|
|
Main list of things:
|
|
|
|
- [Rice cooker](http://ali.onl/128Y) ($26.40 + $3.16 S&H - The star of the show.)
|
|
- [Thermistors](http://ali.onl/128Q) ($2.97 - 100pcs, for temperature readings)
|
|
- [NodeMCU](http://ali.onl/128R) ($2.47 - To, hopefully, allow me to WiFi control the whole thing)
|
|
- [Relay](http://ali.onl/128V) ($0.76 - To switch power on and off.)
|
|
- [ESP8266 Relay](http://ali.onl/128T) ($2.91 + $0.14 S&H - Alternative to the NodeMCU + Relay pairing I'm planning on using)
|
|
|
|
While I have dabbled with Arduino before, this is a far more ambitious project than I have yet done.
|
|
Ideally, I will have the rice cooker serve an API, which my Orange Pi will bounce requests across to as dictated by a frontend hosted on the same machine (this resolves CORS, while still allowing options to control the rice cooker by other devices).
|
|
|
|
For now though, I am away from home, working, so I can't do anything on this for at least another 2 weeks, probably 3.
|
|
Many of my parts have arrived (rice cooker, thermistors, relay, and NodeMCU), so once I get home, I can hit the ground running.
|
|
|
|
# Thoughts
|
|
|
|
## Heating
|
|
|
|
The contents of the rice cooker should be considered when heating/cooling, as they will absorb the heat and thermal lag will be an issue.
|
|
If possible, look into either weighing the contents for a rough approximation (hard/complicated) or use recipe provided portion sizes to calculate the thermal capacity of the contents (water, mainly).
|
|
|
|
# API
|
|
|
|
I tentatively (with no real experience designing them) plan on my API being something like the following.
|
|
|
|
*Italicized* = Description
|
|
|
|
- /sensor/temperature - *Returns temperature*
|
|
- /action/light/kill - *Stops all light activity*
|
|
- /action/light/set - *Change lighting mode, with optional duration*
|
|
- /action/temperature/kill - *Stops all heating/cooling, lets the cooker cool to room temperature alone*
|
|
- /action/temperature/set - *Heat/cool to given temperature, then hold. Should allow setting a target heat/cool rate. Should allow setting a hold duration*
|
|
- /routine/cook/list - *List known cooking routines (proxy to `/settings/cook/recipe/list`)*
|
|
- /routine/cook/start - *Start a routine*
|
|
- /routine/cook/kill - *Kill any current running routine*
|
|
- /routine/cook/schedule/list - *List any scheduled routines*
|
|
- /routine/cook/schedule/set - *Submit/modify/delete a scheduled routine*
|
|
- /settings/lighting/list - *List lighting modes*
|
|
- /settings/lighting/set - *Submit/modify/delete a lighting mode*
|
|
- /settings/cook/warm/temperature - *Set post-cook warming temperature*
|
|
- /settings/cook/warm/set - *Turn post-cook warming on/off*
|
|
- /settings/cook/warm/duration - *Determine post-cook warming duration*
|
|
- /settings/cook/recipe/list - *List known cooking routines*
|
|
- /settings/cook/recipe/set - *Submit/modify/delete a cooking routine*
|
|
|
|
# Cooking schedule definition specifications
|
|
|
|
Directives are distinct actions to be taken.
|
|
|
|
They include:
|
|
|
|
### Sleep
|
|
Just wait for given duration, or until a given condition is met.
|
|
|
|
### Heat
|
|
Heat for a given duration, or until a given condition is met.
|
|
|
|
### Cool
|
|
If I someday choose to use a fan, this should be an active feature.
|
|
Instead, it's the same as `Sleep` for now.
|
|
|
|
### Temperature
|
|
Heat/cool to given temperature, optionally at a given rate of change (may be difficult for cooling if no fan is included).
|
|
This should just be a proxy directive to `Heat`, `Cool`, and `Sleep`.
|
|
For now that should work, but in due course, with tuning and benchmarks, this should run cooling at a variable rate.
|
|
Heating should be fine be fine with fairly large PWM, as the thermal lag I expect to be significant, and we want to try to hit our deadline as quickly as possible.
|
|
|
|
# Dep Graph
|
|
|
|
<img src="/static/rice/connections.svg">
|