If there's a Google WiFi access point 1.5m away, just buy an Ethernet cable and connect the CCU directly into one of the Ethernet jacks on that Google WiFi access point. That could cause the CCU to see very poor signal quality in the 5GHz band and fall back to 2.4GHz instead.Īll of that said, the CCU has an Ethernet jack in the power supply. If you have a wireless subwoofer, a wireless surround sound system, or even just a set of wireless gaming headphones nearby, they are very likely to be using the same part of the 5GHz band that Google WiFi does, and using it in a way that makes sharing that spectrum almost impossible. If that doesn't work, then the most likely explanation is interference. I would first try just unplugging the CCU after the Google WiFi network is up and stable, then plug the CCU in and see if it does a better job of connecting at 5GHz to the nearby access point. This is more likely if you have restarted the Google WiFi network without also restarting the CCU. It's possible it's connecting to the primary Google WiFi unit at 2.4GHz rather than the closer secondary access point. It will just do a signal quality scan on startup and pick the best option. So, it's highly likely the CCU isn't getting those "band steering" hints in the first place. However – and this is an important "however" – fixed devices like the CCU almost never implement 802.11k and 802.11v. But, the decision is still theirs – Google/Nest WiFi can't force them to do anything. Google/Nest WiFi "band steering" is really just an implementation of the 802.11k and 802.11v standards, which let it give clients some extra information they can use to make better decisions about which access point and which band to connect to.
Hello CCU will be making the decision about which band to connect to.
0 kommentar(er)
