Wifi issues

[tuxotron]

I bought my Ionic on Sunday and I couldn't get it to connect to my home wi-fi. Tonight playing around with another router I have at home, the watch connected without any issue.

My current router is an Asus RT-AC88U and my 2.4Ghz band is configured to use AES as WPA encyption, and my watch is NOT able to connect.

Now, I have another router, a Buffalo WZR-600DHP. My 2.4 band is configured to use TKIP/AES. This is a mixed mode that allows clients to connect using TKIP or AES. In this case my watch CAN connect.

So, I thought the problem could be the Ionic doesn't support AES authentication. So on my Asus router, the one the watch CANNOT connect, I created a guess network without any authentication (open network) and the Ionic IS ABLE to connect.

So, it seems that the Ionic cannot handle the AES authentication. 

Can anybody confirm this?

Thanks

[SunsetRunner]

Hi

The ionic can connect to these networks:

Your Fitbit watch can connect to open, WEP, WPA personal, and WPA2 personal Wi-Fi networks. Your watch won’t connect to 5GHz, WPA enterprise, or public Wi-Fi networks that require logins, subscriptions, or profiles. If you see fields for a username or domain when connecting to the Wi-Fi network on a computer, the network isn’t supported. For best results, connect your watch to your home or work Wi-Fi network. Make sure you know the network password before connecting.

Note that you can connect your watch to a personal hotspot which lets you share the cellular data of your phone or tablet when you don’t have access to a Wi-Fi network. Additional data charges from your mobile carrier may apply.

Tip The ionic will not able to connect to wifi if the battery is below 25%

--<-@

[tuxotron]

@SunsetRunner

You are correct about the Fitbit watch can connect to open, WEP, WPA personal, and WPA2 personal Wi-Fi networks.

At least in my case, the problem is when the Wi-Fi only allows for AES encryption authentication. If the Wi-Fi accepts a mixed mode (TKIP/AES), then the watch can connect, I am guessing is because the watch is using TKIP and not AES in such case.

I also tried with an open network and it worked too. I haven't tried WEP or WPA, only WPA2.

My home network uses WPA2 with AES only. My current router doesn't allow for TKIP/AES looks like. Hopefully this is something can be fixed in the firmware of the watch.

Thanks

[winb83]

Use WPA instead of WPA2 and you can set it that way

[tuxotron]

@winb83

Thanks for your suggestion, but I don't think to drop your home Wi-Fi security to WPA is a good idea. 

I submitted a feature suggestion (https://community.fitbit.com/t5/Feature-Suggestions/Ionic-Add-support-for-AES-authentication-on-WPA2...) and hopefully they take it into consideration and implement it. 

In the mean time, when I need it, I create a temporary open guess network in a different segment of my internal home network.

Thanks

[SunsetRunner]

Chang wifi channel to be in the middle range channels for 2.4ghz and make it viable. That should help pairing. Once done, you can set the wifi back. 

[winb83]

It isn't something I permanently do I am just doing it to transfer over some music or when I need an update. When finished I restore the security. It's a temp workaround.

[jason99si]

I'm having the exact same issue. I have the same router, and same WI-FI configuration, and I'm not able to connect with either my new Ionic or Aria 2 scale.  Interestingly, I have an Aria 1 scale that I never had an issue with.

Tuxotron, did you ever find a workaround?

Fitbit, can you help us?

[tuxotron]

@jason99si my solution for now is to enable a guest network temporarily using WPA-Auto-Personal with TKIP-AES (you can also leave it open) and make sure your phone and watch are both connected to that new guest network.

Once I am done, I disable the guest network.

Good luck!