{"id":1482,"date":"2012-01-14T10:35:17","date_gmt":"2012-01-14T16:35:17","guid":{"rendered":"http:\/\/www.wiredprairie.us\/blog\/?p=1482"},"modified":"2012-01-25T20:09:23","modified_gmt":"2012-01-26T02:09:23","slug":"nest-thermostat-review-update-8","status":"publish","type":"post","link":"https:\/\/www.wiredprairie.us\/blog\/index.php\/archives\/1482","title":{"rendered":"Nest Thermostat Review, Update #8"},"content":{"rendered":"

Summary\/Index<\/a><\/p>\n

A few new things have occurred since I last posted.<\/p>\n

\"image\"<\/a>January 11, 2012: Nest Labs updated the firmware of the thermostat to version 1.0.6. There isn\u2019t any publically available information about what was updated however other than \u201cbug fixes.\u201d Thanks to GregN<\/strong> for pointing it out. Here\u2019s a link to their current software releases and updates for anyone interested:<\/p>\n

http:\/\/support.nest.com\/customer\/portal\/articles\/246009-nest-learning-thermostat-nest-mobile-software-updates<\/a><\/p>\n

This week, one of my thermostats in \u201clearning\u201d mode wiped out some of the set points I had specifically added for the weekend (this has happened before). I have no rational explanation for why it would do this as our weekend schedule on the floor where it happened is routine enough that it shouldn\u2019t have made that choice. Nest Labs support suggests turning off \u201clearning\u201d mode when this has occurred to see if it\u2019s related to learning mode. They apparently don\u2019t have a way to track the causes or triggers unfortunately (a debug log would come in very handy now). I turned it off for the time being and have added the deleted set points to see if the problem occurs again.<\/p>\n

UPDATE: 1\/25\/2012:<\/font>  One of our thermostats that still has \u201clearning\u201d turned off decided that our morning set points for our first floor weren\u2019t important and deleted them. Apparently, we didn\u2019t want the house to start warming before we got out of bed. <\/p>\n

I found an interesting issue with the Away Temperature settings that you\u2019ll want to watch out for until they fix it (as it could affect triggers for \u201cauto away\u201d).<\/p>\n

Essentially, there are values that when you put them into the away temperature field, they won\u2019t \u201cstick.\u201d You won\u2019t necessarily notice this right away unless you click around:<\/p>\n

\"nestrounding\"<\/a><\/p>\n

In the video (GIF) above, you\u2019ll see how the \u201c58\u201d won\u2019t stay 58F. It switches to 57 (it happens with 60F as well). I\u2019ve sent a support request to Nest about the issue (they responded the following day and said they\u2019d look into it). Since their web API deals with Celsius, I speculate it could be a rounding issue in their JavaScript code.<\/p>\n

Update: 1\/24\/2012<\/font> The bug appears appears to have been corrected in the few places I happened to check earlier today (as I\u2019m not their QA team, I didn\u2019t check around much \"Smile\").<\/p>\n

Randal<\/strong> pointed out that there was someone who\u2019d done some analysis<\/a> of the temperature readings of a working Nest thermostat (compared to another thermostat). I\u2019d concur that the readings do seem to be far more consistently accurate on the Nest thermostat on average and that our house is more comfortable. However, I\u2019m certainly aware that this comfort will come at a cost. The house is more consistently warmer (now in the heating season). So, depending on your old thermostats and how you handled the temperature in the house, you may find your heating costs rise a bit. Simple way to compensate: you may be able to turn down the thermostat a few degrees! \"Smile\" The temperature may read lower, but the actual temperature may be closer to what you had grown accustomed to. We may do that.<\/p>\n

I\u2019m still trying to understand why \u201cAuto Away\u201d is sometimes triggered when I wouldn\u2019t expect it. I believe that once it was because the \u201caway\u201d temperatures were one degree LESS than the typical set point. So, the house would not \u201csee us\u201d around, and compared the day time (at work for example) set point (60F) to the \u201caway\u201d temperature (59F) and activate the \u201caway\u201d mode. I found the issue with the away temperature above when I was trying to make everything match one evening this week.  The problem with Auto-away activating is that your scheduled set points won\u2019t be used until it is overridden via the remote interface or locally.<\/p>\n

Update: 1\/25\/2012<\/font>: Apparently, auto-away unfortunately can trigger even when the temperature settings match exactly. (Even when there\u2019s nothing to do). I don\u2019t understand what it\u2019s \u201cauto-awaying\u201d from. <\/p>\n

Here\u2019s a few relevant tweets from @Nest<\/a>:<\/p>\n

\"image\"<\/a><\/p>\n

Although I admit to not understanding the topmost tweet. My tweet had been:<\/p>\n

\"image\"<\/a><\/p>\n

I honestly didn\u2019t feel like trying to clarify again in 140 characters.<\/p>\n","protected":false},"excerpt":{"rendered":"

Summary\/Index A few new things have occurred since I last posted. January 11, 2012: Nest Labs updated the firmware of the thermostat to version 1.0.6. There isn\u2019t any publically available information about what was updated however other than \u201cbug fixes.\u201d Thanks to GregN for pointing it out. Here\u2019s a link to their current software releases […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true},"categories":[5,6],"tags":[49,48,45,47,46],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pd5QIe-nU","jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":1382,"url":"https:\/\/www.wiredprairie.us\/blog\/index.php\/archives\/1382","url_meta":{"origin":1482,"position":0},"title":"Nest Thermostat Review, Update #4","date":"January 2, 2012","format":false,"excerpt":"Update #6, Update #5, Update #4, Update #3, Update #2, Update #1, Install A bit more about my Nest thermostat experiences. On the weekend, I spoke with a support engineer from Nest regarding the issue I was having with one of the Nest units failing to properly read the room\u2026","rel":"","context":"In "General"","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.wiredprairie.us\/blog\/wp-content\/uploads\/2012\/01\/image_thumb.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":1420,"url":"https:\/\/www.wiredprairie.us\/blog\/index.php\/archives\/1420","url_meta":{"origin":1482,"position":1},"title":"Nest Thermostat Review, Update #6","date":"January 4, 2012","format":false,"excerpt":"Update #5, Update #4, Update #3, Update #2, Update #1, Install I didn\u2019t expect to have another post so soon. But, the Nest experience continues to frustrate and baffle. On the 3rd of January, I took the following screen shot of our basement schedule for heating: Tonight (one day later\u2026","rel":"","context":"In "General"","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.wiredprairie.us\/blog\/wp-content\/uploads\/2012\/01\/image_thumb4.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":1749,"url":"https:\/\/www.wiredprairie.us\/blog\/index.php\/archives\/1749","url_meta":{"origin":1482,"position":2},"title":"Nest Update #12: Software at 3.0 with New Features","date":"October 3, 2012","format":false,"excerpt":"As the blogosphere exploded yesterday with news of a second generation Nest thermostat and a new major version of the software (for the thermostats and the controllers such as the web site and various SmartPhones), I wondered what impact the new software and hardware would have on average users, like\u2026","rel":"","context":"In "Recommendations"","img":{"alt_text":"IMG_0630","src":"https:\/\/i0.wp.com\/www.wiredprairie.us\/blog\/wp-content\/uploads\/2012\/10\/IMG_0630.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":1340,"url":"https:\/\/www.wiredprairie.us\/blog\/index.php\/archives\/1340","url_meta":{"origin":1482,"position":3},"title":"Nest Thermostat Review, Update #1","date":"December 27, 2011","format":false,"excerpt":"After a few weeks of using the Nest thermostat, I\u2019ve got a few more comments that I\u2019d like to share. (Here\u2019s my post about the installation). The learning feature honestly hasn\u2019t been very useful in the first few weeks. It\u2019s apparently easily confused by days that you're home unexpectedly (for\u2026","rel":"","context":"In "General"","img":{"alt_text":"image","src":"https:\/\/i0.wp.com\/www.wiredprairie.us\/blog\/wp-content\/uploads\/2011\/12\/image_thumb3.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":1576,"url":"https:\/\/www.wiredprairie.us\/blog\/index.php\/archives\/1576","url_meta":{"origin":1482,"position":4},"title":"Nest Thermostat Review, Update #10: Wifi Settings Missing","date":"March 24, 2012","format":false,"excerpt":"One more brief update about our Nest thermostats. After a few weeks of limited use of our HVAC system due to a very unusually warm late winter and early spring, I\u2019d set the whole house to AWAY mode last evening. However, a bit later, I heard the furnace running. Odd.\u2026","rel":"","context":"In "Recommendations"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1432,"url":"https:\/\/www.wiredprairie.us\/blog\/index.php\/archives\/1432","url_meta":{"origin":1482,"position":5},"title":"Nest Thermostat Review, Update #7","date":"January 7, 2012","format":false,"excerpt":"Update #6, Update #5, Update #4, Update #3, Update #2, Update #1, Install I received a replacement thermostat earlier this week as promised by Nest Labs. I had time this afternoon to do a swap and reinstall. Nest had asked me to swap the thermostats between two floors experimentally to\u2026","rel":"","context":"In "General"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.wiredprairie.us\/blog\/index.php\/wpjson\/wp\/v2\/posts\/1482"}],"collection":[{"href":"https:\/\/www.wiredprairie.us\/blog\/index.php\/wpjson\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wiredprairie.us\/blog\/index.php\/wpjson\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wiredprairie.us\/blog\/index.php\/wpjson\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wiredprairie.us\/blog\/index.php\/wpjson\/wp\/v2\/comments?post=1482"}],"version-history":[{"count":3,"href":"https:\/\/www.wiredprairie.us\/blog\/index.php\/wpjson\/wp\/v2\/posts\/1482\/revisions"}],"predecessor-version":[{"id":1517,"href":"https:\/\/www.wiredprairie.us\/blog\/index.php\/wpjson\/wp\/v2\/posts\/1482\/revisions\/1517"}],"wp:attachment":[{"href":"https:\/\/www.wiredprairie.us\/blog\/index.php\/wpjson\/wp\/v2\/media?parent=1482"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wiredprairie.us\/blog\/index.php\/wpjson\/wp\/v2\/categories?post=1482"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wiredprairie.us\/blog\/index.php\/wpjson\/wp\/v2\/tags?post=1482"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}