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.

Can't find 8 digit code to set up Nest WiFi point

Team83
Community Member

Hi--

After being away for more than 6 months, I am re-adding 2 Nest WiFi Points (Model H2E) to an existing network. (They worked fine before I disconnected them.) When I go to "add a new device", I am asked for an 8 digit code (NOT a QR code).

Where do I find this? I cannot find it in the rim of the grey area of the device. Without these Points, my mesh network is very limited. Thx in advance. 

NB. I unplugged and plugged the Nest Wifi Router back in. I created a new "home" network. I dumped the Google Home app and started over. Still no way to bypass page when I'm asked for an 8 digit code. : /

1 Recommended Answer

Team83
Community Member

TY for doing that. I hope a Google rep sees my comment below.

I solved it! There is a tiny 8 digit code on the bottom of the device *underneath* the QR Code sticker. So I was able add said Nest Point to the network and expand the mesh.

I do find it incredible that the design (and method of engraving essential information) impedes the DIY process. Why make critical device #s hard to find or hard to read? I've seen a lot of frustration here about NOT being able to find this information, either in this forum or in the "Help" documents. I like to think Google is known for good design.

All the best. Matter resolved.

View Recommended Answer in original post

8 REPLIES 8

olavrb
Platinum Product Expert
Platinum Product Expert

The 8 digit code is engraved into the rubber ring. More info:


I don't work for Google.

Team83
Community Member

Hi olavrb. 

I've checked the grey rubber ring (see my original note above) after reading that very same post you shared. The engraved sequence on the bottom of my device goes like this:

Model: H2E Google FCC ID: 6 digits Made in Vietnam 14 digits

No unique or distinct 8 digit # is to be found. Nor is there an option to add QR code (which I actually have). I've also done a search in this forum for better answers; can't find them either. I find this all very surprising bec. Google products are usually so intuitive and easy to manage. : /

olavrb
Platinum Product Expert
Platinum Product Expert

Roger that. I escalated the thread, let's hope Google reps can figure it out. 🙂


I don't work for Google.

Team83
Community Member

TY for doing that. I hope a Google rep sees my comment below.

I solved it! There is a tiny 8 digit code on the bottom of the device *underneath* the QR Code sticker. So I was able add said Nest Point to the network and expand the mesh.

I do find it incredible that the design (and method of engraving essential information) impedes the DIY process. Why make critical device #s hard to find or hard to read? I've seen a lot of frustration here about NOT being able to find this information, either in this forum or in the "Help" documents. I like to think Google is known for good design.

All the best. Matter resolved.

EdwardT
Community Specialist
Community Specialist

Hi folks,

 

@olavrb, thanks for the help!

 

@Team83, thanks for reaching out and I'm glad to hear that you were able to find the 8 digit code on the device. We appreciate users who are keen on sharing with us their thoughts. We'll take this as feedback. We're always here if there's anything else you need.
 

Thanks,

Edward

Jeff
Community Specialist
Community Specialist

Hi, all.
As we got our resolution here, I'm going to mark this one as resolved within the next 24 hours. If anyone still needs anything, please feel free to let me know and I can keep things open. Thanks to all who helped and contributed!
Thanks,
- Jeff

olavrb
Platinum Product Expert
Platinum Product Expert

How about making a Google support doc on how to find this 8 digit code? Including info saying that it might be under a sticker, and that it's engraved into the rubber ring?


I don't work for Google.

Jeff
Community Specialist
Community Specialist

That's actually a good idea, olavrb. We actually had a discussion about that in this week's meeting! It remains to be seen if we can get the documentation updated, but it's definitely a good idea.