cancel
Showing results for 
Search instead for 
Did you mean: 

Nest Yale Lock won't connect to nest connect

BeeKeeperDave
Community Member

None of the “fixes”  online have worked - not going to set up a network without security as it has been suggested.   

1 Recommended Answer

Hi ButlerBank,

 

I appreciate the thorough breakdown - you've done the heavy lifting by ruling out proximity and power issues. Thank you for your patience in troubleshooting this.

Since your other Nest devices are working, the app is likely hitting a “handshake” error while trying to use them as “assisting devices”. To bypass this, please try these targeted steps:

  • Temporarily unplug your Nest Camera and doorbell. This forces the app to pair the Lock and Connect directly without interference from other devices.
  • Go to your iPhone's Settings then Privacy & Security then Local Network and ensure the Nest app is toggled ON.
  • “Forget” any old Nest/Yale entries in your phone's Bluetooth settings, then toggle Bluetooth off and back on.
  • Keep the lock keypad illuminated by touching it during the pairing process to prevent the radio from entering sleep mode.

I know it has been a long two days of troubleshooting, but isolating the connection is often the key to clearing a stuck Wi-Fi handshake. I look forward to your update.

 

Regards,

Humberto

 

View Recommended Answer in original post

8 REPLIES 8

humbertogarcia
Community Specialist
Community Specialist

Hi BeeKeeperDave,

 

Thank you for posting in the community! I understand that you’re encountering issues connecting your Nest Yale lock to your Nest Connect and that the online solutions don’t work. Because you don’t want to use the option to set up a network without security, I’m happy to investigate this further with you.

To find a secure solution, I need to know more about the situation:

  • What’s the error message you receive (if any)?
  • What have you done to resolve the inconvenience?
  • Do you know if your Wi-Fi router is currently using WPA3 encryption, or is it set to WPA2/WPA3 Mixed Mode?
  • Are you using a single router, or a mesh Wi-Fi system?
  • Are you managing the lock in the Nest app or the Google Home app?
  • How far is your Lock from the Connect?
  • Are there any walls, mirrors, microwave appliances, or Bluetooth devices between the Connect and the Lock
  • Can you check the Nest x Yale Lock’s battery level?

Please provide the information requested above so I can proceed with the solution evaluation.

 

Regards,

Humberto

I have the same issue Humberto.  After having and using a Nest Yale lock and Nest Connect for years now, the keypad stopped responding.  I fixed that with a full reset of the lock and new batteries, but lost my wifi connection in the process.  I deleted the lock and have been trying to add it back in for two days now.  Reset my router/modem, reset my phone (iOS) reset the Connect and reset the lock. Set my phone to wifi only.  The lock and Connect are only about 4 feet apart, but I also tried using an extension cord so the lock and Connect were literally touching (close enough?).  I have a doorbell and inside camera on the network that are working fine.  My phone finds the Connect immediately, no problem.  Ready to move on to a new product line.  Any thoughts?  Thank you!

Hi ButlerBank,

 

I appreciate the thorough breakdown - you've done the heavy lifting by ruling out proximity and power issues. Thank you for your patience in troubleshooting this.

Since your other Nest devices are working, the app is likely hitting a “handshake” error while trying to use them as “assisting devices”. To bypass this, please try these targeted steps:

  • Temporarily unplug your Nest Camera and doorbell. This forces the app to pair the Lock and Connect directly without interference from other devices.
  • Go to your iPhone's Settings then Privacy & Security then Local Network and ensure the Nest app is toggled ON.
  • “Forget” any old Nest/Yale entries in your phone's Bluetooth settings, then toggle Bluetooth off and back on.
  • Keep the lock keypad illuminated by touching it during the pairing process to prevent the radio from entering sleep mode.

I know it has been a long two days of troubleshooting, but isolating the connection is often the key to clearing a stuck Wi-Fi handshake. I look forward to your update.

 

Regards,

Humberto

 

Thank you Humberto!  I moved the Connect and then got it all to work, just as Amazon was delivering my new Schlage lock with wifi built in.

Brewdude42
Community Member

My Yale Lock kept disconnecting from the Nest Connect.  I went through days of trying to get my nest connect to work with my Yale lock.  First I thought the Nest connect had failed so I bought another one.  New one also didn't solve the problem.  The next solution I tried was buying a single band 2.4 GHz router. That also didn't work.  After trying the old and the new Nest connect several times I connected both of them to my router and that WORKED.  No idea why, but now I have two Nest Connects plugged into one outlet.  I am leaving a good thing as is.  

Brewdude42
Community Member

Whoever is out there reading this my fix may sound crazy, but it worked.  I spent several days/weeks on getting my Yale Lock to connect to the Nest connect.  I bought a new one, I bought a 2.4 GHz single band router.  I drank a few beers.  Then (not sure why or how) I had both my old and new Nest connects plugged in and working.  Then I could get the Yale Lock to connect.  It has been working since (several weeks now).  And I am not touching another thing.  Just putting it out there for the community to read.  Cheers.  And have a GROOVY Holiday.  

BeeKeeperDave
Community Member

I’m still unable to get NEST Connect and Yale lock to “talk” to each other 😞

 

im not  “ techy” but can manage things when explained simply.  

im connected on a 2.5 network (guest) main is 5

please help 

ButlerBank
Community Member

The thing that finally got my lock and Connect to talk was to move the Connect away from the door/lock but closer to the router/modem, but still relatively close to both (a few feet).  Worth a shot.  Never tried 2.4Ghz, so everything is on 5.0.