Connectivity difficulties between Aria and Comcast/Xfinity routers

[JuanJoFitbit]

Hi everyone! It has come to our attention that some users are experiencing issues with syncing/setting up Aria scales with Comcast/Xfinity routers and we are currently reviewing. 

There is a workaround that has helped most users. For this, follow the instructions below:

• Log into comcast/xfinity account
• Once logged in,  visit https://internet.xfinity.com/more
• Edit wifi settings under "Additional Settings"
• Click on 2.4 frequency edit button.
• Select g/n, hit save.
• When the screen refreshes, click edit again, select b/g/n and hit save. 
• Stand on scale
• Continue with the regular setup process

Thank you all for your patience. Any update available, I'll make sure to share it in this thread.

[Timberwolf620]

There is no longer an option for b/g/n and this has been confirmed by Comcast. The 802.11b protocol is no longer supported in its latest modem/router.

You and your "Team" can put it where the sun doesn't shine.

Sent from my iPod

Moderator edit: merged reply

[anjmanda]

I have done this work around and it only lasts 2 weeks until my scale won't sync to the app any more. I then have to go through these steps again and try to connect about 15 times (between my phone and computer) before it finally does. All the while, the aria settings say that it is connected to my internet. Any solution?

[Sarmarmun]

Sorry, I don't have any further suggestions!

[CherylFoster]

My Aria has also stopped working and I go through the process as told check everything with Comcast and I end of with WiFi Err every time. The aria had connected to the 5GHz and I can’t get it to stop. I was told I needed to connect it to the 2.4GHz with 802.11b but Comcast only has a 802.11 b/g/n I am hoping that right please help me this is beyond frustrating 

[Solmors]

This workaround ended up fixing my connection issue. I will be setting up one of my old routers just for this scale so I can get my main network off 802.11b. I find it absurd that Fitbit is using the IEEE 802.11 standard from 1999 (https://www.actiontec.com/wifihelp/evolution-wi-fi-standards-look-802-11abgnac/). 

[Sarmarmun]

Connecting to b/g/n is fine! Give it a try and see if it works!

--
*Sarah Mundell*

[CherylFoster]

I have repeatedly and it still tells me WiFi ERR

I can’t even get the work around to work!

Moderator edit: merged reply

[rhal4d]

setting my router to b/g/n got the scale to sync once before it stopped working again. I have spent hours on these ridiculous workarounds. The Aria is relatively expensive because of the wifi feature. I could get a scale at Target for $29 if I wanted to input the measurements myself. Get it together Fitbit. I've been a loyal customer since 2009 and I'm frustrated by the lack of support on this issue.

[SunsetRunner]

Quick update - pitched the Aria, bought a Renpho, self-bricked my ChargeHR2 and bought a Garmin Fenix 5.

My family will never waste another dime on a FitBit product...and neither will anyone that takes my advice!

[sylvaink]

I have the exact same issue here. I tried to go with no security (no password) on my 2.4Ghz and then just not broadcast the SSID. I tried and it worked!

I got excited and was already envisioning myself sharing the solution to y'all. I reverted back to password, would not work, reverted to no password + no SSID broadcast and this time it won't work. My guess is that if you try enough times at some point it will work, but drive you nuts along the way.

[SteamboatJeff]

I’ve mentioned this in prior posts to this thread already but you can work around the issue by adding an inexpensive WiFi backwards compatible router to your personal Comcast network.

Just plug the secondary router into your Comcast modem using an ethernet cable and follow the setup instructions for the new router. Once the router is operating, follow the normal Aria setup procedures. (You will now have two wireless access points to Comcast. One through the integrated comcast modem/router and another through the new router. Both SSIDs will be visible to your wireless devices.)

This will have you back up and running for $30 or less. Feel free to keeping hating Fitbit if you want but just know that you have an option for this problem. 

[drmeiswinkel]

Cheryl,

This has been the experience of so many of us.  There does not appear to be any plan from Fitbit to make it right.

My advice is to return it if you can.  No matter what you do, replacement will likely be your best option. A lot of us have had very good results with a bluetooth scale drom Renpho.

This is where I think we’re all landing.  I have been contacting media.  I encourag others that are as outraged.  Fitbit isn’t inclined to do something to fix this.  No visible effort to make it right.  And, nothing but circular references to the same impotent schemes.

Moderator edit: merged reply

[SunsetRunner]

Sorry Jeff, I choose to invest in tech that works, not piss away another $30 on circa year 2008 tech that doesn’t. 

[SteamboatJeff]

Riveted, good for you. You should start an string offering recommendations for tech investments. Apparently I’m mistaken about this conversation. I thought it was intended for people experiencing a common problem to collaborate on helpful solutions. Somewhere it’s been hijacked by a minority of trolls spewing personal attacks and mean spirited comments. 

[drmeiswinkel]

Jeff,

i think the work around you posted could be a valid ploy.  It was an helpful post.  

Calling frustrated owners haters wasn’t helpful..  

I think the tech suggestions are useful.  But, chiding or attacking the customer base, then Fitbit is not putting effort into support, isn’t helpful.  It’s best not to provoke people who are already riled.

I am glad your work-around is working.  I look forward to posts from you that tell us if it is stable over time.  I resent, as someone who also bought the product, that you had to resort to putting money into your Aria to make it work.  You, like the rest of us, deserve better from Fitbit.

[SteamboatJeff]

drmeiswinkle, none of my posts call anyone a hater. It’s interesting that you personalized my comments that way then misrepresented my words in two future replies. My reference to the word hate was simply reaffirming my very first post, which indicates that I’m not defending Fitbit in my replies. I hope you are enjoying a healthy lifestyle, which is what all this noise is about anyway.

[drmeiswinkel]

You’re right, you didn’t specifically aay Hater.  I put that in quotes

”...This will have you back up and running for $30 or less. Feel free to keeping hating Fitbit if you want but just know that you have an option for this problem. ”

This may be a working solution.  But you took it to a patronizing and judgmental conclusion. I will give you the respect that comes with expecting you know the meaning of your own words.  

This is a judgement about how people are choosing to respond to your solutions.  It also condones what Fitbit has taken as a tack for remedies.  

While your solution may work, it is unsatisfactory for me.  I have spent $200 on the Aria.  Another $30, for what may prove to be permanent or transient, is not acceptable.  It should not be to you either.  But if it is. don’t belittle the others, with these issues, because they will not do as you have.   Fitbit still needs to be spending resources to support its product lines.

[Sarmarmun]

So, my workaround from above stopped working for me as well... the scale is no longer syncing... I'm not going to waste my time on this one anymore.

[sylvaink]

I tried with an old wifi access point as others have suggested, I used an Apple Airport Express, it does not work either.

It has everything needed on paper, so the problem is probably not coming from the Comcast router.

For reference, here is the post https://community.fitbit.com/t5/Aria/Aria-won-t-connect-to-Apple-Airport-Express/m-p/2911119#M29102

[Pinkzebraholic]

Any new updates on this issue?