Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Index Scale no longer connects

daryljmullen
over 4 years ago

Has anyone fixed this yet?

I‘m unable to connect to WiFi. 
Tried all the suggested fixes splitting the WiFi signal, using the stick, using hotspot, resetting etc. 

Something clearly happened a couple of weeks ago. 

Come on Garmin the forum is littered with dozens of similar posts. 

  • 0 over 4 years ago

    Issued fixed!  It was related to DNS. 

    I have the router provided by ISP and I connect it to an Asus router that has much more features and wi-fi power.  I setup all my wi-fi network using this Asus router.  

    I was changing the DNS configuration to 8.8.8.8 in this router and the scale was not connecting.  Then I noticed that the DNS in the router provided by ISP was set to 1.1.1.1, so I changed it to 8.8.8.8 as well.  Some hours later I tried to use the scale again and it worked perfectly!  

  • 0 over 4 years ago in reply to NILTONHC

    So Garmin is not a bad guy after all ;)

    Scales are not broken :D

  • 0 over 4 years ago in reply to bat0nas

    Yep, it is Cloudflare which cause faults, not only problem and not only Garmin. There is also NTP related problems, this is under server clock.garmin.com, very old problem and new case again. 

  • 0 over 4 years ago

    Yet another person using 1.1.1.1 that spend the last weeks trying to find a solution. Thanks to you guys for the answer, Garmin would never have been able to fix it. Switched to 9.9.9.9 and all is well.

    GARMIN PLEASE FIX YOUR SOFTWARE. 

  • 0 over 4 years ago in reply to rob61280

    Thanks a lot for that tip, I looked into that. I also run a pi-hole.

    I removed Cloudflare (1.1.1.1) from the pi-hole's DNS settings and now the scale syncs again.

  • 0 over 4 years ago

    Scales have been slow at updating my weight recently. It eventually works. I tried debugging it tonight, but nothing stands out. Just a bunch of DHCP, NTP, and DNS calls.

    19:33:40.185369 IP 172.16.21.1.bootps > 172.16.21.135.bootpc: BOOTP/DHCP, Reply, length 300
19:33:40.241052 ARP, Request who-has 172.16.21.1 tell 172.16.21.135, length 60
19:33:40.241166 ARP, Reply 172.16.21.1 is-at 74:83:c2:0a:ae:7d (oui Unknown), length 28
19:33:40.243284 IP 172.16.21.135.56994 > 172.16.21.1.domain: 38162+ A? clock.garmin.com. (34)
19:33:40.246466 IP 172.16.21.1.domain > 172.16.21.135.56994: 38162 1/0/0 A 204.77.162.174 (50)
19:33:40.286083 IP 172.16.21.135.65534 > 204.77.162.174.ntp: NTPv4, Client, length 48
19:33:40.413673 IP 204.77.162.174.ntp > 172.16.21.135.65534: NTPv4, Server, length 48
19:33:41.968603 IP 172.16.21.135.65534 > 204.77.162.174.ntp: NTPv4, Client, length 48
19:33:42.072065 IP 172.16.21.135.56994 > 172.16.21.1.domain: 29119+ A? gold.garmin.com. (33)
19:33:42.095054 IP 204.77.162.174.ntp > 172.16.21.135.65534: NTPv4, Server, length 48
19:33:42.096553 IP 172.16.21.1.domain > 172.16.21.135.56994: 29119 3/0/0 CNAME gold.garmin.com.cdn.cloudflare.net., A 104.19.147.86, A 104.19.148.86 (196)

  • 0 over 4 years ago in reply to paulgrav

    Oh and the name resolution does not change, regardless of whether I use Google or Cloudflare resolvers.

  • Former Member
    0 Former Member over 4 years ago

    I finally figured mine out after not being able to connect for about 6 month. WoW! 

    1.) Take batteries out for 1 minute

    2.) Hold reset button 1 minute

    3.) I then went to my app in settings, I turned off 'bluetooth" under the "Connect App" and then turned it back on. (try this while close to the scale) 

    4.) Then went back to the "Connect App" itself and was able to find the "Index Scale" and it finally connected and allowed me to set it back up with all users.

    TALK ABOUT FRUSTRATION! I WAS LITERALLY GETTING READY TO THROW THE DAMN THING AWAY AND GO BUY A DIFFERENT SMART SCALE.

    HOPE THIS WORKS FOR EVERYONE ELSE! GOOD LUCK.

  • +1 over 4 years ago

    I’m unable to sync my index smart scales as of repairing my device this morning (they had been working fine for a year but due to phone change I had to reconnect). Tried changing the DNS settings to 8.8.8.8 but no luck. Anyone any ideas? It’s infuriating that such expensive technology can cause so many problems. This should be simple stuff.

  • 0 over 4 years ago in reply to jimm_89

    Nope. I tried raising the issue on here a few months ago and the forum moderators flagged my post as abusive and deleted it.

    Garmin doesn't care now that they have your money. I'm never buying their stuff again.