iOS 16 + Private Wi-Fi Address OFF = STILL Disconnecting
This is a continuation of the LONG thread found at:
The short version: New iPhone 14 Pro with iOS 16. The Private Wi-Fi Address option has been turned OFF so that the iPhone can use a reserved IP address set in the Eero Pro 6 (latest firmware). Go to bed, all is working correctly; wake up, the iPhone is now DISCONNECTED from the Wi-Fi and has to be reconnected. This also still happens to a variety of similarly-configured, stationary iPads running iPadOS 15.7. The issue occurs randomly with devices that are all in a 1500 square foot condo.
WHY HAVEN'T YOU FIXED THIS, EERO? It's been happening for over a year now, almost two years. I'm sick of your laziness. TALK TO APPLE AND GET IT FIXED.
I think -- after all this time -- that I may have figured out how to stop this problem. I think it has something to do with the iCloud Keychain. Since most of my Apple devices stay at home all of the time -- iPads set up to be used as TVs -- they don't get used on different WiFi networks or for non-TV stuff, so I turned OFF the iCloud Keychain (Settings > iCloud account > iCloud > Keychain = OFF). The only device where this is still turned on is my iPhone 14 Pro.
Since I made this change last week, I have not woken up to find my iPhone disconnected from WiFi, and there have been no other disconnections of other devices.
It's too early to say that this has definitely solved the issue, but anyone else seeing similar problems should give this a try and see if it helps.
As for the folks at Eero: You need to set up a test for this and see if you can reproduce the problem. Here are the particulars:
- Set up WiFi network with long password (26 characters or more) and SSID with long name (14 characters or more) -- two Eero Pro 6 routers
- Multiple Apple devices (iPhone, iPad -- I have 6 devices) with Keychain = ON
- WiFi on each device with Private Wi-Fi Address = OFF
- All devices have reserved IP address in Eero
I should not have to turn Keychain OFF -- your work in troubleshooting this issue is NOT done even if this does eliminate the issue.