Tangently: I don't quite buy the prewarming use case, the only halfway legitimate use case for a internet connected oven is if you are the type to worry if you left the oven on.
Tangently: I don't quite buy the prewarming use case, the only halfway legitimate use case for a internet connected oven is if you are the type to worry if you left the oven on.
> The only reason I can think of is so you can have a different error message for "the oven service is down" and "unable to access the oven service".
To the user, there is no difference, because the user wouldn't take different corrective action for each case. How can the user correct it if the appliance's cloud service is down? Just ping your own cloud service and if it doesn't respond, tell the user "Unable to access the oven service. Check your Internet connection, and if it's fine, please wait a bit more."
Also reaching out for NTP and keeping the time updated is useful.
But yea, keeping these internet of shit devices on their own VLAN and monitoring what they are up to leads to a lot of 'um, what is going on' moments.
Of all appliances in my kitchen the oven makes the most sense to have network features. Fridge perhaps a distant second, and that's only because I really wish I knew my compressor had failed and could've rescued the $350+ of groceries that spoiled if something had alerted me to the temp rising while the compressor was still attempting to run.
Do they still sell ovens without a timer? Mine (which is quite old) requires setting the time in advance. Forgetting is simply not an option.
Of course, they could start selling ovens without timers to stimulate the sales of internet-connected ones...