←back to thread

280 points RyanShook | 10 comments | | HN request time: 0.325s | source | bottom
1. jajuuka ◴[] No.45144413[source]
Didn't those come out in 2012? That's better than most appliances.
replies(4): >>45144416 #>>45144533 #>>45144827 #>>45145185 #
2. delfinom ◴[] No.45144416[source]
Worse than most thermostats that aren't made by Google though.
3. wrs ◴[] No.45144533[source]
Which says something about how bad modern appliances are.
replies(1): >>45145801 #
4. bluGill ◴[] No.45144827[source]
my car is from 1999 and I can still keep it working. I replaced a perfectly working furnace from 1973 a couple years ago (nearly double the efficiency). I still use my 1939 tractor and can get parts for it. I have plenty of other appliances older than that - many modern ones don't work as well
5. asdff ◴[] No.45145185[source]
Most thermostats last for decades and decades. It is simple equipment.
replies(1): >>45145769 #
6. jajuuka ◴[] No.45145769[source]
Kind of an apples and oranges comparison though. Analog and simple digital thermostats are very simple while something like the nest is running 32-bit OS. Complexity increases cost.
replies(2): >>45146155 #>>45154249 #
7. jajuuka ◴[] No.45145801[source]
Only if you look at appliance official support windows. In terms of energy consumption, efficiency, noise, storage area, weight, and regular maintenance modern appliances are pretty amazing.
8. willis936 ◴[] No.45146155{3}[source]
>Complexity increases cost

Not really. The BOM of a smart thermostat is nearly equal to a dumb one right now. What adds cost is reliability. Hardware reliability costs engineering time and expensive component choices. Software reliability requires engineering resources and a mindset beyond optimizing quarterly returns.

There is no legitimate reason a fancy thermostat should be e-waste after ten years.

replies(1): >>45154265 #
9. asdff ◴[] No.45154249{3}[source]
Why does it need to be complex? It is just managing temperature same as the analog one. Same wires to the furnace and ac. Setting a schedule shouldn't require a heavy OS on top of this. One way I came up with in 5 seconds, just have it sit on the network and take in emails with your schedule changes and you're done. Or just ping it, don't even need the mail setup. Should be pretty light and performant with not very many lines of code.
10. asdff ◴[] No.45154265{4}[source]
To be fair the cheapest thermostat sold at homedepot is probably super reliable since it is using a very simple hardware stack. It isn't like this stuff really ought to go wrong very often. Maybe you break a solder I guess over a lot of heat/cool cycles? It's just a thermometer and a switch.