cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

Integrating Omada Access Point with Google Home

dwkurfman
Community Member

I added a hard-wired Omada EAP615 Outdoor access point to my network. Same SSID and Pasword enabled as the Google points. It seems to work great with my phone. While I don't expect it to be managed from the Google Home app, I expect existing devices (such as a Google Hub or Google Camera) to connect to it and continue to be visible and controllable in Google Home. While I was testing last night, basically shutting down Google points and rebooting devices to ensure they reconnected, I found that Google devices seemed to think there was no network, and that non-Google devices would connect, but Google Home would say they were off-line. 

From everything I've read, this should work. Any pointers on what I am missing?

On the flip side, it's my understanding that if I were to go to an all Omada system in the future, Google Home runs in the cloud, so I shouldn't need to make dramatic changes. I should still be able to use the Google Assistant to turn devices on and off, right? 

 

1 Recommended Answer

Angel,

 

Thanks for responding! I was struggling to find the thread here to post an update.

I reached out to TP-Link to see if there was an issue with Client Isolation. That is documented as being off by default. The person that responded gave me a list of things to check, including (using the TP Link Controller) confirming whether the "client" device, the Google Camera, had an IP address. The Google Camera did not. So, I knew the Google Camera was connected to the Access Point, and that data communications had occurred, becasue I could also see the data transmit/receive information on the console. That led me to "assume" that this was an isolations issue. Then it occured to me to take one of my tablets out in the garage to ensure the new access point had the strongest signal, and stop and restart wifi on the tablet. What I saw was what appeared to be an authentication "hard loop" with WPA errors/warnings repeating. I went back to my PC and saw the tablet was connected, again with no IP address, so starting reviewing the authentication protocols. Everything looked good. Then, in an "oh duh" moment, I realized that I had typed the Modem password in when setting up the credentials for the new Access Point, not the Router password. So, devices were connecting but not authenticating. And, since the focus was the garage, pretty much everthing was cameras/IoT devices, which don't provide any useful feedback. So, changed the password, recycled everything, and the issue was resolved. Again, because I could see devices connecting and exchanging data (which is more granular than what I see on Google Home) I assumed everthing was functioning as it should. Just part of learning to recognize new patterns.

 

Thanks for chiming in! I appreciate it.

 

Dan

View Recommended Answer in original post

2 REPLIES 2

aperezdeleon
Community Specialist
Community Specialist

Hi there dwkurfman,
 
Thanks for reaching out to our community.
 
Creating a network that covers your entire home can be confusing, so let's see what's going on.
 
Your Nest devices can be connected under different access points. The main requirement is for those access points to communicate with each other.
 
Some access points have a setting called "Client Isolation" that prevents connected devices from communicating. Client isolation could also prevent the access point from fully communicating with other devices, making it act as an extender instead of a mesh network node.
 
Ensure your Nest devices have the same IP addresses on both access points.
 
I recommend contacting the manufacturer of your access point to help with these settings alongside answering compatibility questions.
 
Let me know how it goes.

 

Regards,
Angel.

Angel,

 

Thanks for responding! I was struggling to find the thread here to post an update.

I reached out to TP-Link to see if there was an issue with Client Isolation. That is documented as being off by default. The person that responded gave me a list of things to check, including (using the TP Link Controller) confirming whether the "client" device, the Google Camera, had an IP address. The Google Camera did not. So, I knew the Google Camera was connected to the Access Point, and that data communications had occurred, becasue I could also see the data transmit/receive information on the console. That led me to "assume" that this was an isolations issue. Then it occured to me to take one of my tablets out in the garage to ensure the new access point had the strongest signal, and stop and restart wifi on the tablet. What I saw was what appeared to be an authentication "hard loop" with WPA errors/warnings repeating. I went back to my PC and saw the tablet was connected, again with no IP address, so starting reviewing the authentication protocols. Everything looked good. Then, in an "oh duh" moment, I realized that I had typed the Modem password in when setting up the credentials for the new Access Point, not the Router password. So, devices were connecting but not authenticating. And, since the focus was the garage, pretty much everthing was cameras/IoT devices, which don't provide any useful feedback. So, changed the password, recycled everything, and the issue was resolved. Again, because I could see devices connecting and exchanging data (which is more granular than what I see on Google Home) I assumed everthing was functioning as it should. Just part of learning to recognize new patterns.

 

Thanks for chiming in! I appreciate it.

 

Dan