Hi All,
I have a Hub 5 and i'm trying to connect 2 x Nest Protect smoke\Co2 alarms to the WiFi but it keeps failing. After speaking to Nest support they say it is due to the Hub not doing IPv6, is there any plans to roll this out?
How do other Virign Hub use this Nest product if at all?
Kind Regards
Jason
7 years and still waiting, you aint kidding.... guess if you want Nest Protect don't have Virgin which is annoying.
not doing IPv6 - that class one highland cattle excrement !
"it keeps failing" - what is the "it" that falls over ? what are the error messages ?
That is Nest platform issue.
https://support.google.com/googlenest/answer/9263646?hl=en
Old but I searched for IPv6 since I joined the forum anyway. It's really disappointing to hear Google blame this on lack of IPv6 - that's just not the case. IPv6 is _very_ nice to have, though even if I had IPv6 from Virgin it wouldn't change much personally - I'd prefer to use my own IPv6 space via tunnels to a VPS where BGP is possible anyway, so I'm not dependent on the physical link to my home network (I can change ISPs, use multiple ISPs, etc, without any impact to my network).
But... I'm not remotely a realistically average person for a lot of reasons (cost, technical complexity, complete lack of privacy online as anyone can find my full legal name and address easily), and IPv6 has benefits for everyone. No more NAT, no more being affected by rate limits imposed on others in your home/office, access IPv6-only services likely to start appearing as IPv4 gets increasingly expensive and difficult to obtain, etc.
Google, however, are definitely not in that latter category (they have a lot of IPv4 space) and their products all support IPv4... their support should know this, not blame something unrelated to the actual issue.
I suspect the Nest unit a 2.4GHz only device is not able to connect to the 802.11ax / Wi-F6 service of the Hub 5.
HI jasuk7 👋.
Thanks for reaching out to us, Apologies in the delay in responding. As Client62 has stated. Networking systems such as Nest devices including security and health and safety devices will require a network that is 2.4ghz only, IPV4 & IPV6 are unrelated to this issue. They are a system that requires a minimal amount of bandwidth to operate. As WIFI capabilities are changing the one thing that is staying the same is 2.4ghz and making devices that require to talk to like minded devices along with compatibility will always be retained on a 2.4ghz network with a variable of IPV4 & IPV6 as they are flexible in that department but not a requirement.
Should you need any further assistance on the connection of these devices please reach back out to us.
Sabrina
Personally, if I was relying on devices for my family's safety I'd want them connecting via something more reliable than a VM Hub's WiFi.
hi,
it's a problem reconnecting the nest protest i know. using hub 5 had too contact nest ,got it working in the end
got it working in the end -- Please detail exactly how it was made to work
I would like to say it is due to lack of IPv6 but they are talking nonsense. I have a Nest Protect Alarm that worked no problem on the Virgin Hub (Not on Virgin any more though) possibly was on 2.4 band. The only issue I know is the Google Thermostat's did not like the option to set to the 20/40/80Mhz width option. I think from memory I had to set to 20/40Mhz so may the same for the Nest Protect speakers seem happy regardless and can dual stack IPv4/IPv6
