cancel
Showing results for 
Search instead for 
Did you mean: 

WiFi Presence Sensing - network not supported

Basan
Community Member

Hi all,

Recent update now allows for WiFi presence sensing in the Home App however when ever I access it and click add network, and then select my WiFi network I'm connected to on my phone, it says Current Network Not Supported?

Any ideas?

Phone: Pixel 8 Pro

Android 16 QPR2 beta 1

Home App preview enrolled

WiFi: 2.4gzh, 5ghz, 6ghz on WiFi 7

WPA3 security

 

1000007566.png

12 REPLIES 12

ArtyMarty
Community Member

Same here. 

Frequency:  5 GHz /2.4 GHz 

Security:  WPA/WPA2-Personal

Pixel 10 pro xl

Android 16 Build: BD1A.250702.001

GabrielaG
Community Specialist
Community Specialist

Hi everyone,

 

Thank you for reaching out. I'm sorry to hear that your WiFi presence sensing isn't working with your network. I'm glad to help you with this. 

To troubleshoot more effectively, I'll need some additional information from you.

  • When did the issue start?
  • What type of devices have you connected in the Google Home app?
  • Who is your Internet Service Provider?
  • Have you recently made any changes to your home network?

I look forward to your response so we can find a solution for you soon.

 

Regards,

Gabriela

Basan
Community Member

Hi Gabriela,

Issue started last week, shortly after the Wi-Fi presence sensing feature was deployed to the Google Home systems.

Devices connected in the Google Home App - Google Doorbell 2, Outdoor Nest Cam (x2), Hub Mini, Hub Max, Pixel Tablet, Philips Hue Bridge / Light Bulbs, Yale Connexis Smart Front Door Lock, Sony Bravia TV's (x2).

ISP = Vodafone UK

No recent changes made to home network.

 

GabrielaG
Community Specialist
Community Specialist

Hi @Basan,

 

Thank you for your reply. I appreciate the time you took to respond to my post and the information you provided me. It is my pleasure to continue assisting you. Please try these steps to attempt to resolve the issue:

  • Connect the phone explicitly to a 2.4 GHz or 5 GHz SSID only. Avoid automatic band steering between them during setup.
  • Verify that Google Home has “Always allow location access” and that presence sensing is enabled.
  • Reinstall the app. 

Hope this helps, and please let us know if you have any other questions.

 

Regards,

Gabriela

Basan
Community Member

Hello,

I tested splitting my network into 2.4ghz and 5ghz, and connected to each one individually - same error.

Google Home as "Always allow location access" and presence sensing is enabled (already using phones location as the presence sensing) - tried turning this off and back on, same error.

Reinstalled the Google Home App - Same Error.

Tested on another device - Pixel 7 pro & Samsung Zfold 4, enabled presence on both of them 1 by 1, and tried to add wireless network - same error on each.

jpmacdo
Community Member

Any answer on this?

 

Basan
Community Member

Unfortunately not, and still an issue within my environment. Even set up a new wireless SSID using WPA-2 security and it doesn't look it.

Even went as far as digging out my old Google WiFi router, hooking that up and putting the SSIDs through there but ... Even from googles own product ... Same error of Current Network Not Supported.

Vcaddy
Community Member

Same issue as OP, also already tried workarounds mentioned above but ended with the same problem.

 

P.S: when i try to add my wifi network it does not say its not supported. However, the app freeze for abit then crashes.

Wifi 2.4, 5.8, and 6 ghz

Mostly smartlife devices (Tuya) are added and a couple Xioami robots.

Oasis81
Community Member

News on this?

Someone fix it pls?

Same error since few days 

Basan
Community Member

Unfortunately no responses from anyone.

As some additional information - I updated to the next Android 16 QPR2 Beta 2 release yesterday ... still same issue.

Vcaddy
Community Member

I think the issue is that google seems to be migrating to a new google home (OS/platform) backend services causing all these issues. As if you try making new routines you have new options and the whole thing looks quite different. If nothing shows up, try switching assistants back to back then clearing app cache & data .. if still the same then try logging to google home through your browser.

 

Btw... while i still cant add my home wifi to presence sensing. However, location based automations are working perfectly (albeit if you are able to save them without errors).

 

And lastly, google you suck ass, I majored in programming and can barely keep up with your hidden fragmented crap wtf get ur **bleep** together.

Basan
Community Member

So since the last update of the OS, as well as some Home App updates, I've done some more testing.

TLDR: Google still suck when developing new features / WiFi Presence sensing seems to only work when the security of the Wi-Fi channel is lowered to WPA / WPA2

-------------------------

Set up secondary WiFi SSID which was using 2.4Ghz / 5Ghz as normal

Set for WPA2 / WPA3 security (the current standard) with my devices automatically choosing WPA3

Disabled the 5ghz DFS mode just  in case it was this causing the issue with it using higher than Channel 48 which is restricted in some countries

Outcome: Same issue

-------------------------

Split the SSID into 2.4Ghz and 5Ghz specifically - same settings as above - tested both SSID's individually

Outcome: Same issue

-------------------------

Merged SSID's back together and re-enabled DFS mode (back to normal)

Lowered Security to WPA/WPA2

Phone connects and uses WPA2

Wi-Fi Sensing now allows you to add the network

-------------------------

So basically - Brand new feature from Google - only works when you intentionally lower the security of your Wi-Fi network to a level with known exploits and attack vectors - good job Google, leading the way in the technology innovation as always!

With that being said .... Hopefully ... this is just a bug, with it being an in development feature ... but would love some actual feedback from Google to say "hey .. yeah sorry, we F'ed up *again* with a new feature and we're working on it"