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.

Try Moving Closer to Another Nest Device

xKernalSandersx
Community Member

Hello,

I have been having the most frustrating experience trying to get my Nest Cam (battery) going, I have two of these devices and it's occurring on both. It keeps stating "Try Moving Closer to Another Nest Device" which I am literally having it sit on top of my Nest wifi router as well as a Nest Speaker....and it still says I need to move it closer. I get all the way through the setup to this point and I have been unable to get these things set up.

I am using the Google Home App on my Pixel 6 - I have never had such an issue with any other device and wondering if anyone has a solution that isn't finding an iOS device to set it up, or having to create a second home for these to live in.

2 Recommended AnswerS

GrahamMills
Community Member

Hey

I just managed to resolve this very annoying issue which I had when trying to add a nest cam battery and nest cam indoor v2

TLDR
Remove the Nest Hello Wired then re add after adding your current gen camera.

I was getting the "Try Moving Closer to Another Nest Device" message for both cameras.

I tested creating another home and they added fine to that, but the issue is you can move them to the original home and no aware subscription. However this did mean that they were working, updated firmware etc.

After several attempts and contacting support with no successful suggestions, I decided to debug myself.

I have basically the following devices:

- Nest Wifi
- Nest Hello doorbell wired
- Some nest small speakers
- Hub v1
- Protect v2
- Some Nest cam outdoors
- Thermostat v3

3rd party
- Android TVs
- Hue
- Tapo plugs

 

I turned off the Hub, Protect, Hello to start with and tried again.

When adding the Cam Indoor to my main home I now got an error along the lines of trying to get wifi details from the nest hello. So that was bit more useful.

As I thought It might be the hello that it was originally trying and failing to get config from (now offline) I thought I'd remove that from the configuration.

I removed it (hello) from the home via the nest app and tried again.

YES, both the cameras now added successfully. The first added and set up and the second I think got its config from the first camera now in the home.

I then turned things back on and added the hello back which configures itself from the nest protect.

I can only assume at this point that its a config sync/network issue between previous and current gen nest devices. The new nest cams try to get the config from the Hub, Protect or Hello but for some reason aren't quite compatible.

 

I hope that helps you get your Cam added.

View Recommended Answer in original post

xKernalSandersx
Community Member

Hello,

So my solution was a bit wonky but after 90 minutes on the phone with Google I decided to delete my home, remove all linked accounts and set up a new Home. This did fix the issue and I was able to successfully get all cameras and devices working!

View Recommended Answer in original post

6 REPLIES 6

Brad
Community Specialist
Community Specialist

Hey there,

 

I am terribly sorry to hear that you're having this issue! I would love to assist you with this issue. If you are having issues with your Nest Cam or Nest Doorbell, I would suggest that you first start by restarting it. 

 

Restart: Keeps all your settings, and it should reconnect to the same Wi-Fi network. This is helpful if it ever becomes frozen, has trouble reconnecting to the internet, or isn't working normally.

 

Best regards,

Brad

GrahamMills
Community Member

Hey

I just managed to resolve this very annoying issue which I had when trying to add a nest cam battery and nest cam indoor v2

TLDR
Remove the Nest Hello Wired then re add after adding your current gen camera.

I was getting the "Try Moving Closer to Another Nest Device" message for both cameras.

I tested creating another home and they added fine to that, but the issue is you can move them to the original home and no aware subscription. However this did mean that they were working, updated firmware etc.

After several attempts and contacting support with no successful suggestions, I decided to debug myself.

I have basically the following devices:

- Nest Wifi
- Nest Hello doorbell wired
- Some nest small speakers
- Hub v1
- Protect v2
- Some Nest cam outdoors
- Thermostat v3

3rd party
- Android TVs
- Hue
- Tapo plugs

 

I turned off the Hub, Protect, Hello to start with and tried again.

When adding the Cam Indoor to my main home I now got an error along the lines of trying to get wifi details from the nest hello. So that was bit more useful.

As I thought It might be the hello that it was originally trying and failing to get config from (now offline) I thought I'd remove that from the configuration.

I removed it (hello) from the home via the nest app and tried again.

YES, both the cameras now added successfully. The first added and set up and the second I think got its config from the first camera now in the home.

I then turned things back on and added the hello back which configures itself from the nest protect.

I can only assume at this point that its a config sync/network issue between previous and current gen nest devices. The new nest cams try to get the config from the Hub, Protect or Hello but for some reason aren't quite compatible.

 

I hope that helps you get your Cam added.

Brad
Community Specialist
Community Specialist

Hi there,

Just checking in to see how the conversation is going as there's been a lapse in activity on this thread.

Best regard,
Brad

xKernalSandersx
Community Member

Hello,

So my solution was a bit wonky but after 90 minutes on the phone with Google I decided to delete my home, remove all linked accounts and set up a new Home. This did fix the issue and I was able to successfully get all cameras and devices working!

Brad
Community Specialist
Community Specialist

@xKernalSandersx

 

I am happy to hear that your issue has been resolved! Looks like we can consider this issue resolved. I will lock this thread shortly unless I can help out with something else. 

 

Best regards,

Brad

Hi there,

 

We haven't heard any updates from you. Please let us know if you still need help as we will be locking this in 24 hours if we won't hear back from you again. Feel free to start a new thread and we'll be happy to help.

 

Regards,
Steve