I'm pretty heavily into Google's eco-system and my personal experience with their support desks isn't all roses to be fair. It's not unusual for first/second line helpdesks to be detached from the more complex issues - just one of those things I guess 🤷
I had an issue with a new Chromebook recently where it outright refused to connect to 6GHz WiFi. I raised the issue via the Google bug tracker/provided logs etc. and wit a bit of persistence it was fixed in a ChromeOS update. I'm fairly certain if I'd gone through Google's frontline support teams, I'd have got nowhere 😉
Anyway, in the absence of an update, there is another potential solution if you don't want the hassle of using Compatible WiFi. Instead, you can try changing the security of the default WiFi network to 'WPA3-Personal-Transition'. This is a more established security method that the Pixel devices should have no problem handling. There are a few things to be mindful of though: -
- Some devices don't like traditional mixed security modes, so you may find that other devices on your network then need to use Compatible WiFi. Personally, out of 30+ devices, I don't have anything that struggles but YMMV.
- If something doesn't play nicely and you decide to switch the security mode back, then there's a good chance that newer devices (those that support WPA3) will refuse to reconnect to the WiFi network. To resolve this you would need to 'forget' the saved WiFi connection on said devices and reconnect from scratch.
- If you ever factory reset your hub, it will revert back to WPA3-Personal-Compatibility.
