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

After SW 3.00 - No Networks Found / Invalid Password / Blinking WiFi icon + Red X when syncing

sunspot68
over 1 year ago

Hello,

yesterday my index S2 upgraded to firmware 3.00.

Today I saw that:

User settings were not synced, which means that no usernames are on the scale, only empty persons with question marks.

Date and Time settings are also not synced and do not change after several measurements. (I switched to 24h in the app)

I did:

1) Factory reset

2) removed the scale from Garmin web interface and from the Garmin app

3) Re-attached the scale again via Garmin app (and yes, I of course removed indexS2 from bluetooth settings)

4) Did 2) and 3) several times

5) Tried to install the firmware again via the manual process. Did not work since 3.00 is already on the scale...

6) Deleted the WLAN connection and attached it again

7) Switched to another WLAN

4) Replaced the batteries and did 1), 2) 3), 6) again.

Nothing helped. the scale still does not show the user(s) I attached to the Garmin app and does not sync weight.

And I also noticed that after trying to sync a red X appears in the upper left corner of the scale for a short time.

Any hints?

Regards Uli

  • 0 over 1 year ago in reply to Garmin-Kevin

    Hi,

    1. Yes

    2. Yes

    3. The Netherlands

  • 0 over 1 year ago in reply to SUBRAID

    This is remarkable. Reading that I did some additional experiments with the FritzBox:

    I went to the FritzBox Admin page. Under "WLAN/Funknetz" all the devices which are connected and those which are known are listed.

    I removed all currently not connected devices.

    Then I tried to add the scale to the FritzBox WLAN via GC App. And after refreshing The WLAN/Networks page I see the scales MAC address  as an entry without IP address!

    I clicked on this item and removed it completely using the Reset button in the lower right corner of the page.

    I took out one battery from the scale and put it in again while reset was pressed. After switching the pages on the scale I let the scale try to download the update. It fails.

    But: Looking at the Fritz!Boxs WLAN/Networks page now I see the scale as WINC-00-00 with an IP address.

    This all sounds good, but the data transfer still fails. You can see that from the flashing WLAN icon on the scale.

    Maybe this is useful for and his team.

  • 0 over 1 year ago in reply to sunspot68

    Same in my FritzBox. No transfer. With my old AppleAirportExtreme no Problem. Transfer is perfect. 

  • 0 over 1 year ago in reply to mschoenw

    Saw the possibility of using the phone, Android, internet sharing.
    Security WPA2-Personal
    2.4 GHz band

    This worked. Synchronization registered both in the Connect app and on connect.garmin.com

    As a Wi-Fi router, I use an Asus RT-AX92U, which has worked without problems with the scale version 2.08.
    After the update to ver. 3.00 the Connect app shows that it is the wrong password!

  • 0 over 1 year ago in reply to mschoenw

    Hello, everyone,

    it doesn't work for me with the Fritzbox 7590 either.

    I hung an old AVM FRITZ!WLAN Repeater 310 between the router and scales, set up a new WLAN name and lo and behold, everything works as before. Still hope for help soon.
    (Translated with Google)

  • 0 over 1 year ago in reply to mschoenw

    My scale finds the network and passes the test. But it doesn't sync. It was running ok on old software. Garmin, why are you so lousy on the firmware side? there are always some quirks here and there.

    Of after ten - or - so attemps. It worked. Such a bad stuff :/ 

  • 0 over 1 year ago in reply to mschoenw

    Garmin just updated me on the issue and said my scale needs to be replaced.   My issue no Wi-Fi after upgrade same as posted here.

    THEY WANT TO CHARGE ME $110 TO REPLACE SCALE.  

    THERE SHOULD BE NO CHARGE FOR AB ISSUE CAUSED BY THEM, INFACT THERE SHOULD BE AN APOLOGY. 

    Unbelievable, scale was working fine until they did the 3.0 upgrade.   

  • 0 over 1 year ago in reply to stevegillespie

    Don't think this is necessary , After resolving the issue myself. I have been emailing with Garmin support, I have communicated the issue and have created a workaround, one that at least works on my router. They will get back to me and or post an update here, but I've left it to them to communicate this.. As this might not work on everyone elses setup 

  • 0 over 1 year ago in reply to TheStrat 
    Small correction: The DHCP server actually offers an IP address, but scales seems not detect or honour this offering:

    2023-02-02T22:49:20+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:20+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:20+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:20+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:20+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:20+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:20+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:20+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:22+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:22+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:24+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:24+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:27+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:27+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:31+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:31+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:35+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:35+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:38+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:38+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:42+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:42+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:42+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:42+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:43+01:00 nas dnsmasq-dhcp[18284]: DHCPDISCOVER(ovs_eth0) b4:c2:6a:1f:3c:9f
    2023-02-02T22:49:43+01:00 nas dnsmasq-dhcp[18284]: DHCPOFFER(ovs_eth0) 192.168.10.123 b4:c2:6a:1f:3c:9f