Aria will not connect to network

[pennine]

I have now over an hour trying to set up my Fitbit Aria to my network since I had to change the batteries, and also recently upgraded by internet system to an eero system. I have tried on my mac and iphone repeatedly and always get stuck on the same step.

- I take out the battery for 10 seconds, flip the machine over and press to initiate setup mode

- I wait for the Aria network to appear on my computer or phone and then connect to the Aria network

- Then I try to find the home wifi network on the computer or phone page, but no networks display.

- I am doing this literally right next to the wifi router

- I have done this over 20 times now. No networks ever show up. Ever.

I saw an old community post about this issue from five years ago where the Fitbit person just ran through the same steps that were in the instructions that the poor person had already tried over and over again. I swear to god, if someone from fitbit just links me to a video instructing me to do the same things I have already been trying repeatedly to no avail, I'm taking this thing to the backyard and smashing it to bits with a baseball bat and never buying another fitbit product again. I'm already practically at that point.

Moderator edit: updated label

[SunsetRunner]

Is your network compatible?

Networking Requirements
Aria 2 connects directly to your home’s Wi-Fi network and supports the following
network configurations:
• Wireless 802.11b/g/n, 2.4 GHz standard
• WEP / WPA / WPA2 personal security
• Automatic (DHCP) IP setup (static IP configuration not supported)
Aria 2 requires an 802.11b/g/n-compatible network to connect and sync your scale
data to your Fitbit account.

[kelliott71]

What about the original Aria?  Though I do know it’s network compatible and my husband is no slouch when it comes to network stuff.  Like pennine, I’m about to do some serious damage to this thing. 

[CPNC]

I'm having the exact same problem and it's MADDENING.  I can't seem to get any networks to display and I'm about done with this dumb scale.  

[Minneli]

I had this exactly same problem after I changed my internet router to a new one. After a hundred tries, exactly the way it says in the Help page (https://help.fitbit.com/articles/en_US/Help_article/1873.htm) I was going mad, because I couldn't get the list of available networks in my laptop. But lo and behold - I finally managed!

The trick is: forget the video they are showing you and forget your laptop. ***Use only your phone*** that has the Fitbit app in it (but be sure to use your Wi-Fi in that phone, not the cellular connection). Then do what they tell you to do: take out the battery, put it back, press the corners of the scales, connect your phone to Aria network.

After that I finally got the list of the available networks to show. However, the list didn't show my new router, only my neighbor's, and "Refresh Networks" didn't help. So there was one last hoop to hop through: I tapped Join Other Network and manually wrote the name of my network + the password. And voilá, now my Aria is connected to the new router! 

This shouldn't have been this difficult and take an hour of my life, but I'm happy I finally got it to work. I hope the 11 people who have said "this affects me too" find this helpful. 

[Minneli]

Check my answer to Pennine above. Let's hope it helps you. 🙂

[pennine]

I threw away the scale and bought a different brand.

[BedHeadBoris]

I have been stuck on the “connecting” screen for over an hour now... any ideas? I’m with the same network provider, I’ve only updated my router. At a loss as to what to do 😩

[FitnessFool]

I am in the same situation.  Upgraded my router to a TP Link 6.0 (which includes support for 2.4 and 5.0).  I haven't been able to connect for 2 hours now, and I have tried everything suggested above.  I give up. When my Charge 4 dies I'm done with Fitbit.  You would think that a technology company like Google / Alphabet would make their equipment forward compatible.  Such an embarrassment.

[kelliott71]

Try connecting it to 2.4 instead of the 5.0.  That is ultimately what ended up working for us.