5 ms·
Jup. A family member has Nest thermostats. Server went down. The thermostats cranked up to 30C / 86F as the failure mode. Just makes no sense. I get that you do
by leipert 3y ago
Jup. A family member has Nest thermostats. Server went down. The thermostats cranked up to 30C / 86F as the failure mode. Just makes no sense. I get that you don’t want freezing pipes, if the server goes down, but come on.
- Bluecobra 3y agoThat sounds a bit far fetched to me, I have had my Internet go down multiple times and never have a Nest problem. In fact I don’t even think an Internet connection is required if you just want it to be a dumb thermostat. The default safety settings on my nest is 45F for heat and 95F for AC. This setting is user adjustable so maybe your family member override it.
- deleted 3y ago[deleted]
- leipert 3y agoYou are probably in the US. In Germany usually each radiator has a thermostat and you usually do not have wall thermostats unless you have floor heating. That being said, I’ve double checked and it is Netatmo [0] and not Nest. The point still stands, that some cloud based home automation devices behave stupid if they cannot talk to the server. [0]: https://www.netatmo.com/en-gb/additional-smart-radiator-valve https://www.netatmo.com/en-gb/additional-smart-radiator-valv...
- sgerenser 3y agoI find this hard to believe. The thermostat has a local copy of the heat/cool setpoints, why wouldn’t it just keep using those if it can’t access the server? At a minimum it’s a bug, not just the normal operation when it can’t access the cloud.