<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Wrong away detections AGAIN in Home Automation</title>
    <link>https://www.googlenestcommunity.com/t5/Home-Automation/Wrong-away-detections-AGAIN/m-p/797823#M63351</link>
    <description>&lt;P&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; I wrote "Google never admitted it was a server side issue, and eventually the problem went away by itself." and "as if yesterday I am having the same problem again"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is obvious it's not my problem but Google's problem (again).&lt;/P&gt;</description>
    <pubDate>Fri, 20 Mar 2026 15:37:22 GMT</pubDate>
    <dc:creator>thegios</dc:creator>
    <dc:date>2026-03-20T15:37:22Z</dc:date>
    <item>
      <title>Wrong away detections AGAIN</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Wrong-away-detections-AGAIN/m-p/797776#M63343</link>
      <description>&lt;P&gt;Google Home is AGAIN detecting me as away while instead being at home.&lt;/P&gt;&lt;P&gt;I've had this problem for weeks a few months ago, opened endless cases to Google to no avail, they never admitted it was a server side issue, and eventually the problem went away by itself.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now the problem is back again as of yesterday: I am at home and suddenly my AWAY routine runs for no reason. It happened also tonight. And this morning when I woke up, I picked my phone and the away routine run.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am.jsing both location and wifi for away detection, so the problem must be again a server side issue.&lt;/P&gt;&lt;P&gt;Anyone else?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Mar 2026 06:39:51 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Wrong-away-detections-AGAIN/m-p/797776#M63343</guid>
      <dc:creator>thegios</dc:creator>
      <dc:date>2026-03-20T06:39:51Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong away detections AGAIN</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Wrong-away-detections-AGAIN/m-p/797810#M63350</link>
      <description>&lt;P&gt;if you use VPN or workprofile on the same device it could interfere.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also the location settings are pretty specific. try turning on timeline if you havent yet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the area around you is very crowded with other signals they might push your gps outside of the 'home' zone too. I dont think there is a fix for that.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Mar 2026 14:25:36 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Wrong-away-detections-AGAIN/m-p/797810#M63350</guid>
      <dc:creator>Maxieaxie</dc:creator>
      <dc:date>2026-03-20T14:25:36Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong away detections AGAIN</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Wrong-away-detections-AGAIN/m-p/797823#M63351</link>
      <description>&lt;P&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; I wrote "Google never admitted it was a server side issue, and eventually the problem went away by itself." and "as if yesterday I am having the same problem again"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is obvious it's not my problem but Google's problem (again).&lt;/P&gt;</description>
      <pubDate>Fri, 20 Mar 2026 15:37:22 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Wrong-away-detections-AGAIN/m-p/797823#M63351</guid>
      <dc:creator>thegios</dc:creator>
      <dc:date>2026-03-20T15:37:22Z</dc:date>
    </item>
  </channel>
</rss>

