@metalshark : In the grand scheme of things, would it not be easier to just change the PSK? Not an ideal solution, but a workaround all the same.
I don't believe that pausing the subscription is an option, certainly nothing that has been discussed before or gets referenced in the legal notices for the subscription.
@metalshark I've got to agree with @Mad_Dog_Bravo here. The WPA PSK spec does permit using any ASCII character in the passphrase but it sounds like that isn't working in Stadia's implementation, for whatever reason.
I'd suggest using the in-app Send Feedback option to report this issue to the development team so that they can hopefully fix this in the future but it would make sense to go ahead and change your passphrase to work around this problem in the meantime. Like MDB said, I don't think Google is likely to allow you to pause/suspend your subscription until this gets sorted.
I’ve used the Feedback feature and communicated with them on Twitter (where they asked me to do all the fault finding for them!?!), as well as raising on the Discord. Due to the speed of creating an alphanumeric rainbow table for WPA2 PSKs, am not lowering my security so the controller can work when every other device in the house follows the spec. Plus this is a great indication of how much support to expect out of Google for Stadia going forward.
Here’s the conversation from over a month ago showing them asking me to do the fault finding for them. Now when asking for updates on them fixing it (remembering Chromebooks, Chromecasta, Nest devices, Android and Google Home devices do not have this issue) I just get two emojis. Someone writing and two hands together like a prayer. ✍️ 🙏
Why let your subscription go to waste when you can also play it on a Chrome browser and a Pixel phone if you have one.
Besides, having a special character in your passphrase hardly makes it "higher" security. I'm not sure where you live but if people are constantly trying to hack into your wifi, you need something better than WPA2-PSK.
No pixel phone (or Android to use the sigmaxpi app) and at home have a gaming PC.
Having special characters in your passphrase (as opposed to just alphanumerics) means that creating rainbow tables for your SSID takes a lot longer.
Hopefully Google actually take supporting the product seriously, not going to hold my breath though.
I might be ignorant, but why can't you just stop using the special characters and instead add a few extra regular characters. Isn't it mostly the length of the passphrase that'll add to the complexity? Honest question...