{"id":15421,"date":"2025-04-25T22:11:28","date_gmt":"2025-04-26T05:11:28","guid":{"rendered":"https:\/\/bone-in-the-throat.com\/Blog\/?p=15421"},"modified":"2025-04-26T10:48:56","modified_gmt":"2025-04-26T17:48:56","slug":"oh-goody-google-is-at-it-again","status":"publish","type":"post","link":"https:\/\/bone-in-the-throat.com\/Blog\/2025\/04\/25\/oh-goody-google-is-at-it-again\/","title":{"rendered":"Oh goody! Google is at it again!"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: right;\" title=\"Screenshot 2025-04-25 at 22.05.56.png\" src=\"https:\/\/bone-in-the-throat.com\/Blog\/wp-content\/uploads\/2025\/04\/Screenshot-2025-04-25-at-22.05.56.png\" alt=\"\" width=\"288\" height=\"300\" border=\"0\" \/>I knew it was coming. I just didn\u2019t think they\u2019d move this quickly.<\/p>\n<p>According to an email today, and it was confirmed in the news Google is discontinuing support for Gen 1 and Gen 2 Nest Thermostats.\u00a0<\/p>\n<p>At first thought, I was like no big deal, then I read further into the email and found that not only are they no longer updating the internal software, they\u2019e also going to be killing remote access to the unit.<\/p>\n<p>Basically, my smart machine is going to get just as dumb as a regular thermostat but will retain scheduling ability.\u00a0<\/p>\n<p>This sucks!<\/p>\n<p>No more ability to control the house temperature if I\u2019m away. That doesn\u2019t sound like a big deal, but it\u2019s really nice in winter to have the house in the 50s when I\u2019m away, then tell Siri to warm the house up to something comfortable before I actually get there.<\/p>\n<p>If you\u2019ve got a regular schedule that can be programmed. If you don\u2019t have a regular schedule then you come home to a freezing house and crank the thermostat to warm it up quick.<\/p>\n<p>With either the preprogrammed schedule, or the remote commands, the temp is increased in shorter bursts over a longer time. It\u2019s a bit more balanced and efficient.<\/p>\n<p>I knew Google was going to do this. To their credit they have discounted their newest version of the machine but I\u2019m not interested. Yes It\u2019s a nice machine, expensive, but given how Google is behaving and that they want me to have a full Google account instead of the old Nest account I\u2019m not inclined to get deeper into Google.<\/p>\n<p>What I want is an ecosystem that just talks to HomeKit and does so locally between devices inside the house. I don\u2019t really like even low level stuff like house controls bouncing all over the internet. I was willing to put up with HomeKit, and Google so long as the Thermostat and the Protect smoke were providing what I believe to be a reasonable level of integrated protection.<\/p>\n<p>The night of the fire, the A\/C did kick on and distributed the smoke throughout the house. It also fanned the fire.\u00a0<\/p>\n<p>But with Google\u2019s recent moves,<\/p>\n<p>I\u2019ve been looking at alternatives.<\/p>\n<p>Regardless of my remaining in this house or not, it\u2019s a good point to disconnect from Google. My Thermostat will get dumb in October. I\u2019ve got until then to make some kind of decision.<\/p>\n<p>Trouble is, most of the smart thermostats want an account, and in some cases they want you to have a paid monthly or yearly subscription.\u00a0<\/p>\n<p>That makes me rethink the whole smart thermostat idea. The Nest thermostat saved me money over the years, and while it was under Nest\u2019s control didn\u2019t cost anything beyond the cost of the unit and giving some of my information to Nest via their app.<\/p>\n<p>This new situation may cancel the savings of any potential unit. It might also be a sign that for me, going forward simplicity is the best path.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I knew it was coming. I just didn\u2019t think they\u2019d move this quickly. According to an email today, and it was confirmed in the news Google is discontinuing support for Gen 1 and Gen 2 Nest Thermostats.\u00a0 At first thought, I was like no big deal, then I read further into the email and found &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/bone-in-the-throat.com\/Blog\/2025\/04\/25\/oh-goody-google-is-at-it-again\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Oh goody! Google is at it again!&#8221;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[168,9],"tags":[190,174],"class_list":["post-15421","post","type-post","status-publish","format-standard","hentry","category-annoyances","category-technology","tag-assholes","tag-technology"],"_links":{"self":[{"href":"https:\/\/bone-in-the-throat.com\/Blog\/wp-json\/wp\/v2\/posts\/15421","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bone-in-the-throat.com\/Blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bone-in-the-throat.com\/Blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bone-in-the-throat.com\/Blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/bone-in-the-throat.com\/Blog\/wp-json\/wp\/v2\/comments?post=15421"}],"version-history":[{"count":2,"href":"https:\/\/bone-in-the-throat.com\/Blog\/wp-json\/wp\/v2\/posts\/15421\/revisions"}],"predecessor-version":[{"id":15423,"href":"https:\/\/bone-in-the-throat.com\/Blog\/wp-json\/wp\/v2\/posts\/15421\/revisions\/15423"}],"wp:attachment":[{"href":"https:\/\/bone-in-the-throat.com\/Blog\/wp-json\/wp\/v2\/media?parent=15421"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bone-in-the-throat.com\/Blog\/wp-json\/wp\/v2\/categories?post=15421"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bone-in-the-throat.com\/Blog\/wp-json\/wp\/v2\/tags?post=15421"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}