3 ms·
That depends on what the automated process is. If you live in Alaska, you don't want your heater to switch off if something goes wrong. If you are on holiday,
by Someone 11y ago
That depends on what the automated process is.
If you live in Alaska, you don't want your heater to switch off if something goes wrong.
If you are on holiday, you don't want the software watering your garden to "failsafe" by stopping doing anything at all a week before your return.
- pbhjpbhj 11y agoThe valves in your watering equipment failing open doesn't seem better to me, can't imagine the bill and how flooded the garden (neighbours garden, and house) would be. Perhaps better to leave fail state optional. On the Alaskan situation I'd expect a frost sensor to put the heating on when it fell below 5deg C, or a settable temp, as a separate system to the normal thermostat.
- FussyZeus 11y agoYou're both forgetting that according to the situation as I understand it, NOTHING HAD FAILED, other than the Internet. The NEST thermostat was working perfectly as far as we know. Nothing had broken, it had lost connection to a resource, yes, but that should not prevent it from doing it's job, i.e. keeping the temperature of the home at or near a given temperature.
- Someone 11y ago"The valves in your watering equipment failing open doesn't seem better to me" I was reacting (a bit 'shoot from the hip') to the categorical statement that failing off is the better option. However, as you acknowledge for the heater, depending on the reason for failure, there may be other options. For example, if the humidity sensor fails in a plant watering system, the system could fall back on an average regime instead of shutting down completely. If it has a clock, that regime might be adjusted for the season. The designer of a system should design its failure modes, too.