I wrote a similar real service for IP-enabled high-end coffee makers. Every cup brewed generated a key/value "ping" with brew time, dose, desired and actual tem

I wrote a similar real service for IP-enabled high-end coffee makers. Every cup brewed generated a key/value "ping" with brew time, dose, desired and actual temp, and other cup metadata. These went to a Rails web service which actually did expose REST target endpoints (though they weren't on the coffee maker itself, and one couldn't send a brew instruction). A version of this even tweeted every cup for a while, and that HTTP client was actually implemented on a microcontroller inside the coffee maker.