What protocol is Nest Protect using?

[Hoot_Foghorn]

The Nest App reports my two protect devices are allocated an ipv4 address from the RFC1918 range I'm using on my private LAN. The App also lists the mac address it is using on WiFi.

If I scan my network (a ping sweep) I don't see its IP nor Mac Address.

If one of my Protect devices is greyed out in the Nest App I can't use "normal" tests to check whether the device is on-line, like pinging it, or similar.

The recovery steps Google proposes don't give any indication of what the issue might be, So being able to ping would be the minimal.

So, what IP protocol, Why don't I see its IP or Mac address.. how does a Protect talk to the mothership?

Thanks,

Hoot

[kcruzgonzalez]

Hi Hoot_Foghorn,

Thanks for reaching out to our Nest Community. We are so happy to assist you with your questions about the Nest Protect.

The Nest Protect likely uses a combination of communication methods:

• Local Network (for basic functionality):

  • IPv4: As you observed, it's assigned an IP address within your local network (RFC1918 range).
  • Wi-Fi: It connects to your Wi-Fi network using its MAC address for basic communication and local control.
  • However, this IP and MAC address might not always be visible on your network scan. Some devices might use dynamic IP addresses that change frequently, or they might have firewalls that restrict network discovery.

• Cloud Communication (for features like remote access and notifications):

  • The Nest Protect likely uses a dedicated protocol for communication with Google's servers. This protocol might be encrypted and not accessible through standard network scans.
  • This cloud connection is essential for features like remote access, notifications, and software updates.

Why you can't ping it:

• Security: The Nest Protect might have security measures in place that prevent direct pinging. This is a common security practice to minimize the risk of attacks.
• Limited Functionality: The Nest Protect might be designed to primarily communicate with the Nest app and Google servers, with limited support for other network interactions.

Let me know if you have any further questions.

Regards,

Kevin

[DanCoco]

Regarding ability to p8ng. I have two Nest Protects and was just able to ping both of mine without issues. I assign a reserved dhcp lease to them so ip addresses do not change, but pinging an ip range should produce a reply evwn without dhcp reservation.

To specialist Kevin,

Your mention of why he "might not" be able to ping, is that confirmed by Google documentation, or is that speculation based on general industry practices?

[Patrick_Caezza · Accepted solution]

@Hoot_Foghorn 

The Nest Protect will turn off the Wi-Fi if you have the battery-only ones installed. If you have the hard-wired ones installed, the Wi-Fi will stay on.

It does this to extend battery life on the battery-only model.

If you press the button on the Protect and put it into the "Ready To Test" mode the Wi-Fi will turn back on for a short while