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.

Protect V2 does not connect for writing history

RM59
Community Member

Hi, I have four Nest Protect V2 in my network; three work just fine but one does not check WiFi (Access Point 3m away, signal checks fine) and writes history like the others. It is connected (test with centre-button succesfull) and the app shows connection until after about two days the connection is lost (app shows "gray"). Removing batteries restores connection instantly without problems. Factory reset did not help. Fixed IP-address (mac) did not help either. Recently I experienced an alarm on another sensor and this "problematic" sensor correctly reported alarm as networked device. Suggestions?

1 Recommended Answer

zoeuvre
Community Specialist
Community Specialist

Hi folks, 

 

Thanks for chiming in, @code_

 

@RM59, Uh-oh! I'm sorry to hear that you're experiencing issues with one of your Nest Protect V2 devices not connecting for writing history. Here are a few suggestions to troubleshoot and address the problem:

 

  1. While you mentioned that the Access Point is only 3 meters away, it's worth checking the Wi-Fi signal strength at the location of the problematic Nest Protect device. Even a slight variation in the signal strength can affect connectivity. You can use a Wi-Fi analyzer app or the Wi-Fi settings on your phone to check the signal strength in that area. If the signal is weak, consider improving the Wi-Fi coverage by adjusting the positioning of your Access Point or using a Wi-Fi range extender.
  2. Ensure that there are no potential sources of interference near the Nest Protect device that could disrupt the Wi-Fi connection. Other electronic devices, thick walls, or metal objects can interfere with the signal and cause connectivity issues. Try moving the device temporarily to a different location to see if the problem persists.
  3. Ensure that your Nest Protect devices have the latest software installed. Updates often include bug fixes and improvements that can address connectivity issues. You can check for updates through the Nest app or the Nest website.
  4. Try restarting the problematic Nest Protect device by removing and reinserting the batteries. This can help refresh its connection to the network and potentially resolve any temporary issues.
  5. Some routers have settings such as "AP Isolation" or "Client Isolation" that can restrict communication between devices on the network. Make sure that these settings are disabled or adjusted appropriately to allow communication between the Nest Protect devices and the rest of your network.

 

I hope these suggestions help you resolve the issue with your Nest Protect V2 device not connecting for writing history.

 

Best,

Zoe

View Recommended Answer in original post

4 REPLIES 4

code_
Community Member

Hiya!

I would recommend:

  1. Ensure you're using a network band that is less prone to interference (ideally 2.4ghz band)
  2. Replacing the nest device. If your device is in warranty google should send a replacement.
  3. Ensure you have a strong network signal and the nest protect is in close range as possible.

 

It could be a faulty sensor/something wrong with the nest's protect hardware. 

 

zoeuvre
Community Specialist
Community Specialist

Hi folks, 

 

Thanks for chiming in, @code_

 

@RM59, Uh-oh! I'm sorry to hear that you're experiencing issues with one of your Nest Protect V2 devices not connecting for writing history. Here are a few suggestions to troubleshoot and address the problem:

 

  1. While you mentioned that the Access Point is only 3 meters away, it's worth checking the Wi-Fi signal strength at the location of the problematic Nest Protect device. Even a slight variation in the signal strength can affect connectivity. You can use a Wi-Fi analyzer app or the Wi-Fi settings on your phone to check the signal strength in that area. If the signal is weak, consider improving the Wi-Fi coverage by adjusting the positioning of your Access Point or using a Wi-Fi range extender.
  2. Ensure that there are no potential sources of interference near the Nest Protect device that could disrupt the Wi-Fi connection. Other electronic devices, thick walls, or metal objects can interfere with the signal and cause connectivity issues. Try moving the device temporarily to a different location to see if the problem persists.
  3. Ensure that your Nest Protect devices have the latest software installed. Updates often include bug fixes and improvements that can address connectivity issues. You can check for updates through the Nest app or the Nest website.
  4. Try restarting the problematic Nest Protect device by removing and reinserting the batteries. This can help refresh its connection to the network and potentially resolve any temporary issues.
  5. Some routers have settings such as "AP Isolation" or "Client Isolation" that can restrict communication between devices on the network. Make sure that these settings are disabled or adjusted appropriately to allow communication between the Nest Protect devices and the rest of your network.

 

I hope these suggestions help you resolve the issue with your Nest Protect V2 device not connecting for writing history.

 

Best,

Zoe

RM59
Community Member

Zoe,

thanks for your extensive answer: very much appreciated.

It puzzled me that I was able to register the device to my account and it connected to the network, but next after a few days it just was off-line. Therefore I have been experimenting. I took the device from the ceiling and placed it near the Access Point which it would likely connect with. For days the device worked just fine and wrote its history as advertised. Placing it back on the ceiling it went wrong again. Next I decided to relocate the baseplate and monitored its connectivity. Shifting it just 30 cm away from its original position resolved the issue. Apparently the chimney channel near the "line of sight" (and likely to contain some sheeting) is the cause of interference. So, in short your suggestions 1 and 2 were right. The latest software was installed and resetting it by removing/inserting batteries never worked. 

Finally, it is solved and I am happy to report that I can confirm your suggestions for troubleshooting: "it is the interference, stupid!" Thxs again for your feedback.

Kind regards,

René Meijn

The Netherlands

zoeuvre
Community Specialist
Community Specialist

Hi René, 

 

You're welcome! I'm glad that everything has been sorted out. If you have questions or concerns in the future, feel free to start a new thread, and we'll be happy to help.

 

Regards,

Zoe