Presence sensing error message "Request contains an invalid argument"

[JM14]

When using the Home app, choosing our 4th gen Nest thermostat, then selecting "Presence sensing". There is a section that states

Home devices

These devices have sensors that can detect presence. Ambient noise won't contribute to presence...

The nest thermostat (icon) appears. There is also a toggle switch. When the toggle is switched to the right (selected). The following error message appears:   "Request contains an invalid argument".

Is this normal behaviour? Does this mean that the 4th gen thermostat already detects "presence" so it can't be switched on because it is already on? Any technical insight would be much appreciated!

[Joeria]

Following, I have the same question.

[Aggie96]

Same issue

[Mbigouben]

Same issue. New thermostat 4th Gen. 

[johndavidjohn22]

I ran into the same error with my 4th gen Nest—it seems like a glitch on Google’s side, not something you're doing wrong. The thermostat does have built-in presence sensing, so that might be causing the conflict learn more .

[Mv5]

Same issue here

[Mbigouben]

I was in touch with Google Tech Support and they are trying to figure it out. If i get an update I will pass it along. 

[edwolf]

same issue 

[sfranche]

I have the same issue

[kingnever]

Just got our new thermostat and am having the same issue.  Lame. 

[edwolf]

Called tech support - known issue and they are working on it - lame is right! The feature not working is a key aspect of the product. Annoying! 

[kingnever]

I spent about 2 hours with tech support trying to get it to work to no avail.  I've already got the thermostat uninstalled, boxed up, and ready to return for a refund.

[edwolf]

I’m with you - going to give it a few days to see if they fix the bug - if not it’s going back! 

[Leviosa]

I also got in touch with Google Tech Support. They want to exchange my thermostat with a new one. Unclear to me this will solve the problem. 

[edwolf]

please update - odd request give. this forum on the issue. 

[shoek]

Same issue with my new v4 (replacing a v2 that I used the Nest app to manage)

Interestingly the v2 was working with Google Home Presence Sensing prior to replacing it

[amballin2]

Getting same issue on older nest thermostat and generation 1 of learning thermostat.  Yet other ones I have installed (both versions) show presence sensing is turned on. 

[SylvaBen]

From Google Support:

We've escalated your case to our Higher management, and they've identified that this is unfortunately a widespread emerging issue that many users are currently experiencing. Our engineers are actively working to investigate and resolve it as quickly as possible.

To help us track the impact of this issue and ensure you receive direct updates on its resolution, we kindly ask you to report it yourself through our dedicated Debug Panel. This will provide our development team with crucial data and allow you to be automatically notified once a fix is implemented.

[edwolf]

did they provide a link? thank you. 

[SylvaBen]

https://support.google.com/googlenest/gethelp

[SylvaBen]

But it didn’t seem very helpful. It just brought me here. 

[edwolf]

Well - I'm going to give it. a week and then return my nest and delete the goggle home app for good. ThenNest App Gen 2 was so much better. Pease fix this google! You jane MANY customers who are having a very poor google experience - I am  one of them! 

[Jh72]

Same error for nest protects and other devices used for presence sensing. Not just the thermostat. 

[SylvaBen]

I had manually set the Home app to "Away" and when I came back the Thermostat sensed me present and came out of eco mode, but the app still says away. 

[Leviosa]

Same issue except the error message is "Unable to save settings." 

[MedMark]

Not normal behavior.  I installed (upgraded Gen 2 Learning) 3 Gen 4 Learning 2 weeks ago.  Toggle was selectable and all three worked as intended for home/away.  I have 5 zones so needed 2 additional Gen 4s.  One Gen 4 developed a problem so I exchanged it at the local Google Store and purchased the 2 additional Gen 4s needed.

After installing thermostats three new Gen 4s Memorial Day weekend, none of the new thermostats will toggle in as presence sensors.  The two previously installed Gen 4 thermostats and 2 Protects are still toggled on and functioning for home/away.   

Contacted support and rebooted new T-stats.  De-selected home/away and phone location, then re-enabled.  Same result - prior installed devices function as presence sensors and new installs give invalid argument error.

[DUBinc]

Having the same issue. App says Away when I’m not home but thermostat is still in Comfort instead of Eco mode. Seems like this just started happening over Memorial Weekend. PLEASE FIX THIS GOOGLE 

[Mbigouben]

Just updated Home app on iOS and it seems to have resolved the issue. 

[MedMark]

TY for info.  Updated app and all of my Learning G4 T-stats and Protects now toggle on for presence sensing.  

I have phone location enabled but functionally it is a mixed bag for my application.  I don’t want my HVAC system to go into eco mode when I am in and out of home around local area.  I did submit a request for a geofence parameter that triggers home/away based on a user defined distance from home.  In that way users could enter a distance that most likely indicates no one will be returning to the home for an extended period of time.  If the keyed boundary is far enough, pre-heating/cooling could begin to minimize walking into an excessively cold/hot house.  Have always managed this manually but distance-defined geofencing could solve both needs.

[erezb]

I can toggle again the presence sensing option.

Enabling it is one thing, I only hope Google also fixed the other bugs around home/Away mode.
https://www.googlenestcommunity.com/t5/Nest-Thermostats/Home-Away-going-crazy/td-p/685203

[JM14]

Just in time for the mosquito season, for me at least "THE BUG IS SQUASHED!!!" (re presence sensing error)... probably a lot of bugs "still flying" but with the App update.... this one for me is 'fixed'....

[Leviosa]

Thanks to all community members who raised this issue here or other threads, as well as through contacting support, Google has fixed the issue. It appears to be a Google Nest server-side issue (in the cloud) and nothing wrong with our thermostats or how they have been installed or configured. Magically overnight I am now able to toggle the presence sensing. With the parameter being saved without error.

So yes, I too can enable the setting. However, I have been at home all day so have yet to see if home/away actually works.... 🤔