02-22-2022 08:46
02-22-2022 08:46
Apparently, Fitbit app will NOT work during their WiFi setup IF and only IF the home owner is doing one of the following:
* static MAC filtering at the WiFi router
* DHCP exclusion by MAC address or
* ARP PROXY FORWARDING enabled
These setup are common in complex large-network home routers.
Fitbit App attempts to do WiFi DHCP-IP negotiation with the using of Apple iOS DYNAMIC (PRIVACY-ENHANCING) MAC ADDRESS: stop that, just stop, STOP! It will fail, simply because Fitbit App does not "SEE THAT APPLE ALREADY DISABLED PRIVACY MAC ADDRESS".
The temporary workaround is to find another WiFi that will take on ANYONE (provided that the correct WiFi password is given), which to me is an extremely form of poor network security.
This is why fancy home routers will start filtering MAC addresses during DHCP-IP negotiation. So, the Fitbit App UI designer needs a way to provide an option to DISABLE RANDOM MAC ADDRESS toward the Apple WiFi open WiFi API.
02-23-2022 03:52
02-23-2022 03:52
Hi @ZeCommunityName - if the owner of the router imposes MAC address restrictions you may not get an IP address unless the MAC address for your watch has been authorized. This is nothing to do with Fitbit what restrictions are imposed.
To fix it, look in the watch Settings, About menu for the MAC address of the watch and get it authorized for the network in question.
Author | ch, passion for improvement.