Apple Watch Wifi keeps reverting to private address

Hi there. I updated my Series 3 Apple Watch to WatchOS 8.1 a month or two ago and have run into no end of issues. The latest is this - in both my work and home environment, Wifi is restricted by MAC address, so the concept of "private addresses" won't allow that to work (I want and require my Wifi to know which specific devices are connecting to it). So I have all my Apple devices specifically set to not use private addresses on my networks.


I know that while trying to connect, in Wifi settings, I can touch the SSID name on the watch and then, turn off private address. After it fails the first time, I can then connect again, and since it is now properly broadcasting its MAC address (as all devices should do), it connects and everything works fine. That should be all I have to do.


Except, after the update, it seems to only remember that I want private addressing on my networks for a few days. Every few days, my watch can't connect to Wifi, and when I check it out in settings, sure enough it's going for private addressing again.


Is there a fix for this (or a way to tell it to not use private addressing as a default in general - I don't care if third party Wifi sites recognize me, but I certainly require my own Wifi to do so). It used to work properly prior to my update of WatchOS (but then again, a lot of things used to work properly prior to that....)


Thanks!


Dan

Apple Watch

Posted on Jan 3, 2022 9:22 PM

Reply
Question marked as Top-ranking reply

Posted on Dec 20, 2022 3:04 PM

Keychain access FTW. Hadn't read the post here about removing SSID from Keychain, but that's what I did:


So this worked for me (multiple APs, Unifi). On a Mac I opened Keychain Access and deleted all instances of the home wifi network (from iCloud, User, and I think System keychains). Then I forgot the home Wifi network from all Mac's, iPhone, Watch, and iPad. I verified there were no more home wifi entries in Keychain on another Mac. Then shut down these devices. After a moment I powered on iPhone and Watch, and jointed the home wifi from iPhone. When i checked the watch a few moments later it was already "connected" to the home wifi. Then start up all the devices and share wifi passphrase from iPhone.


I didn't have to mess with HomePods or Apple TV.


My guess is some kind of corruption on conflict in the home LAN passphrase in Keychain. Hope this helps you.

80 replies

Apr 7, 2022 4:54 AM in response to Dan Charrois

I tried to get an update on the ticket via the support chat yesterday. Unfortunately, the support agent was unable to get my inquiry to the department where the ticket was escalated to. Instead I learned, that the only way to get an update was to have another phone call that I am lacking to time for. In addition, given the previous communication with the support, I am afraid to have to go through the whole bug description again.


The problem for us here is that we are in two niches here:

-People with multiple access points and the same ssid

-People that actually care about the correct/standard compliant use of mac addresses


Both these niches will prevent the bug from getting enough attention.


Patrick

May 24, 2022 5:44 PM in response to Dan Charrois

My Apple Watch series 6 has this problem too. It continually reverts to private address in the settings for my home wifi on the watch. NO OTHER APPLE DEVICE does this, they all have private address turned off in the settings for the exact same wifi network. In the end, I think I will just not bother turning it off, sometimes I have to do this twice a day as otherwise it shows up in my unifi ap logs as being denied access.


Same reasons as everyone else here and in other threads -- we NEED to know who and what is connecting to our wifi networks for security reasons.


Had to laugh at the Apple rep's reply tho, how they came to that conclusion of what we're needing is beyond comprehension.

May 25, 2022 4:46 PM in response to PatrickRe

This is another case of it is Apple's way or the highway. As a network admin I would be seething at this feature continually being re-enabled because you need the device to be from a real address and not be changing either as the device roams across various access points in the workplace or home -- I wonder if Apple have ever heard of access lists, MAC address filters and the likes. Perhaps not. Or if they have, then they arrogantly think that everybody needs to adjust to their thinking/mentality without considering some of the reasons things are the way they are to begin with. I support them having the feature but for the love of humanity, please ensure that if a user NEEDS it to be turned off, it turns off and stays off!

Jun 20, 2022 7:12 AM in response to Dan Charrois

I’m sad to say I have the same problem with my Series 7 and Series 3. The 3 I’ve had for years and it didn’t have this problem an update in 2022. Like others, my iPhones and iPad, and MacBooks don’t have this issue, and I have 3 APs transmitting 3 SSIDs. Sure enough, every three days or so my watch is back on a private MAC address instead of its native address. Very aggravating!

Jul 26, 2022 8:16 PM in response to Dan Charrois

I am also having this issue. I have multiple APs all broadcasting the same SSIDs, as others have stated.


Oddly enough, in addition to private address turning itself on, my Watch also doesn't automatically connect to Wi-Fi. The other day, I was cooking in the kitchen. My iPhone in the other room ran out of battery. Watch never switched to Wi-Fi. I happened to glance at it and saw the red crossed-out iPhone icon indicating my iPhone and Watch weren't connected.


I opened settings and re-connected the Watch to my Wi-Fi network. All I had to do was tap on the network name and it connected, so clearly it is remembering the network; however, I also noticed it had ONCE AGAIN turned on private address.


Later, after charging my iPhone up, I turned it off to mimic try and replicate the issue. Sure enough-- Watch didn't switch over to Wi-Fi automatically (gave it 5 minutes). I was able to connect manually via the Watch settings, and private address was turned on again.


This is a house full of Macs, iPads, iPhones, Watches, Apple TVs, HomePods, etc. No other device is having this issue of failing to connect to Wi-Fi automatically, and none of them where Private Address is an option are having that setting reset itself.


[Edited by Moderator] 


Aug 20, 2022 4:31 PM in response to schmeddlap

I have the same issue:

2 access points (Meraki MR33 and Ubiquiti AP), same SSIDs broadcast, different channels.

Apple Watch routinely drops WiFi connectivity without automatically rejoining. After manually joining the wireless network, I have to turn off Private Address.

it’s very frustrating for the same points made previously by others.

I've upgrade my iPhone and Apple Watch to the latest developer betas and this issue still occurs.

Sep 28, 2022 6:24 AM in response to Dan Charrois

I can confirm I’m experiencing the same issue. I have multiple VLANs with different SSIDs.


What makes this even more frustrating, is that I’m ok if the watch only connects to one of the SSID, but if I click on “forget this network”, after some time the watch looks at the stored networks on iCloud and gets the credentials and starts doing this again.


Then I get dozens of logs on my network of different addresses trying to connect, connecting for a few minutes and then dropping the connection. But the watch doesn’t get a successful internet connection so it tries to connect to different networks.


It’s very frustrating and I’m at the point of deleting all the networks from all my Apple devices

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Apple Watch Wifi keeps reverting to private address

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.