I've had this problem with companies, too.
I owned a Belkin router. If the microwave was on, WiFi devices "connected" to the router would lose the connection. The router's front panel LED would go from green to red.
When the microwave was done, sometimes the WiFi would recover … sometimes it wouldn't.
Support agreed that this was a problem and sent me a new router.
It, of course, had the same issue. I sort of understand the WiFi and the microwave interfering. I do not understand why it should persist even after the microwave is off.
Oh well. I later changed to Comcast's router. If you enter in WPA2-PSK key (not a password, an actual key) and you power-cycle the router (which happens automatically on occasion) the router will reset the key to the factor default password. But only the password/key changes, not the SSID or any other settings.
Support agreed that this was a problem and sent me a new router. (I… actually didn't want a new router, I just wanted to make them aware of the issue, but okay.)
And yeah, that one of course does the exact same thing because it's a software bug, not a hardware one, and I'm the only person on the planet choosing a key by random generation.
So now I feed the output from urandom through base64 to make it a password, which goes through whatever KDF (at least, I hope it's a KDF, but my gut doesn't trust WPA2 that much) WPA2 uses just to get random data into more random data. Or, IDK, perhaps I should just give up and declare WiFi patently insecure and just craft a nice riddle for the password.
It is sort of along the lines of something else I've noticed: there are a ton of companies, who, in one way or another, sell software, but have absolutely no public-facing bug tracker, and doom their support agents to just fielding the same bugs all day, which, practically speaking, they likely just /dev/null those reports, and in the same breath, their marketing department will shove the words "valued customer" down your eyeballs.