Related

S2 not uploading to Garmin connect

Maginskee
9 months ago

Scales have worked fine up until today. 

I've reset and checked wifi details, tested the connection of the scales to the wifi from the Garmin connect app; that seemed ok but still fails to upload to Garmin connect.

I then hard reset, connected to the wifi again and once again, after a weight measurement it fails to upload. I then hard reset again and tried on a different wifi network, hot spotting with my phone and the same thing occurs.

Any ideas?

  • 0 9 days ago

    I have the same issue, measurement on the scale are fine all metrics appear and the user is recognized correctly but none of the metric is uploaded to garmin connect

  • 0 9 days ago in reply to Garmin-Eiliko

    I have the same problem all metrics appear correctly on the S2 including user is recognized correctly but they the metrics are not uploaded to garmin connect.

    1. Yes

    2. Yes

    3. The Netherands

  • 0 9 days ago in reply to urli_by

    1. Just checking terminology: segment and subnet do not mean the same thing in router language.  For home routers, segment usually means VLAN.  The router and scale can be on the same subnet but different segments, and not see each other.

  • 0 9 days ago in reply to BerendDeSchouwer

    So, currently I'm waiting for the usb-rj45 adapter to build another network only for the scale.
    I was desperate to connect them to the kinetic network.

  • 0 5 days ago in reply to BerendDeSchouwer

    Unfortunately, didn't help

    Currently, I have the following configuration:

    wifi network 2.4ghz, wpa2-psk dhcp 192.168.10.1, firewall disabled
    84744 1004.249938 0.0.0.0 255.255.255.255 DHCP 303 DHCP Request  - Transaction ID 0xfeca2bc9
    84758 1004.661999 GarminIntern_42:20:dc Broadcast ARP 42 Who has 192.168.10.1? Tell 192.168.10.76

    Scale is unable to establish proper communication with the DHCP server, resulting in a failure to perform essential operations dependent on DHCP. As a consequence, its functionality is impaired, and I am unable to use it for its intended purposes.
     

  • 0 4 days ago in reply to urli_by

    The scale is getting DHCP, since it gets the IP 192.168.10.76.  It's looking for the default gateway (192.168.10.1) or DNS or DHCP server to *verify* the DHCP lease.  DHCP is usually 4 IP packets (two from the client, two from the server), and possibly additional ARP packets.

    This network dump only shows incoming packets, not the router's response, or there would have been a DHCP answer or response logged in addition to a DHCP request.

    ARP isn't working, which means the ARP response is going out on the wrong interface, or isn't accepted on that VLAN, indicating a VLAN/subnet mismatch, but ARP can only happen after the initial DHCP lease (two packets) has been processed; so at *least* the first 2 of 4 packets happened.

    If ARP is not responding (but you don't trap outgoing packets), then it's a VLAN issue; or your router has RP filtering enabled and you've got the same subnet on two interfaces.  That's not part of the firewall, that's part of DoS mitigation, and on Linux is in /proc/sys/net/ipv4/conf/.../rp_filter.

    If ARP is responding, but the scale isn't receiving it, you're hitting the same problem as me, with WiFi encryption.  You need to trap outgoing packets to know.

    Try and put your phone or any other device on that network.

  • 0 4 days ago in reply to BerendDeSchouwer

    next step:
    empty laptop connected to the main wifi network
    on this laptop I'm rised up a hotspot and connect scale to it
    that's all what I see in wireshark:
    1 0.000000 0.0.0.0 255.255.255.255 DHCP 303 DHCP Request - Transaction ID 0xcc95b1b7
    2 0.007669 192.168.137.1 192.168.137.138 DHCP 344 DHCP ACK - Transaction ID 0xcc95b1b7
    3 0.248631 GarminIntern_42:20:dc Broadcast ARP 42 Who has 192.168.137.1? Tell 192.168.137.138
    4 0.248651 56:14:f3:f6:ab:85 GarminIntern_42:20:dc ARP 42 192.168.137.1 is at 56:14:f3:f6:ab:85
    5 0.250493 192.168.137.138 192.168.137.1 DNS 76 Standard query 0x5a1b A clock.garmin.com
    6 0.374259 192.168.137.1 192.168.137.138 DNS 108 Standard query response 0x5a1b A clock.garmin.com A 204.77.162.174
    7 1.375074 192.168.137.138 192.168.137.1 DNS 76 Standard query 0x5a1b A clock.garmin.com
    8 1.376441 192.168.137.1 192.168.137.138 DNS 108 Standard query response 0x5a1b A clock.garmin.com A 204.77.162.174
    9 8.143452 192.168.137.138 192.168.137.1 DNS 76 Standard query 0x5a1b A clock.garmin.com
    10 8.144890 192.168.137.1 192.168.137.138 DNS 108 Standard query response 0x5a1b A clock.garmin.com A 204.77.162.174
    11 15.526255 192.168.137.138 192.168.137.1 DNS 76 Standard query 0x5a1b A clock.garmin.com
    12 15.537050 192.168.137.1 192.168.137.138 DNS 108 Standard query response 0x5a1b A clock.garmin.com A 204.77.162.174


    after this one 
    23 59.207993 192.168.137.138 192.168.137.1 DNS 76 Standard query 0x5a1b A clock.garmin.com
    24 59.218625 192.168.137.1 192.168.137.138 DNS 108 Standard query response 0x5a1b A clock.garmin.com A 204.77.162.174
    25 67.742711 192.168.137.138 0.0.0.0 NTP 90 NTP Version 4, client
    26 68.061973 192.168.137.138 0.0.0.0 NTP 90 NTP Version 4, client

    scale fails with wifi attempt

    Frame 25: 90 bytes on wire (720 bits), 90 bytes captured (720 bits) on interface \Device\NPF_{E7A84A0D-8CFF-4405-8550-E82BA91B291B}, id 0
    Ethernet II, Src: GarminIntern_42:20:dc (14:8f:21:42:20:dc), Dst: 56:14:f3:f6:ab:85 (56:14:f3:f6:ab:85)
    Internet Protocol Version 4, Src: 192.168.137.138, Dst: 0.0.0.0
    User Datagram Protocol, Src Port: 65534, Dst Port: 123
    Network Time Protocol (NTP Version 4, client)
    Flags: 0xe3, Leap Indicator: unknown (clock unsynchronized), Version number: NTP Version 4, Mode: client
    Peer Clock Stratum: reserved (92)
    Peer Polling Interval: 0 (1 seconds)
    Peer Clock Precision: 32 (4294967296,000000000 seconds)
    Root Delay: 512,001877 seconds
    Root Dispersion: 0,000000 seconds
    Reference ID: 48.132.3.0
    Reference Timestamp: Jul 8, 2050 21:56:16.003906250 UTC
    Origin Timestamp: Dec 8, 1988 13:28:32.195327758 UTC
    Receive Timestamp: Feb 7, 2036 06:28:16.003906250 UTC
    Transmit Timestamp: May 12, 2036 02:02:08.000000000 UTC

    after reseting scale and reconnect to hotspot(assign to hotspot address 192.168.137.1 dns 8.8.8.8)
    1 0.000000 0.0.0.0 255.255.255.255 DHCP 303 DHCP Request - Transaction ID 0x25d1b1f1
    2 0.007126 192.168.137.1 192.168.137.138 DHCP 344 DHCP ACK - Transaction ID 0x25d1b1f1
    3 7.975317 0.0.0.0 255.255.255.255 DHCP 303 DHCP Request - Transaction ID 0xd354d95e
    4 7.981886 192.168.137.1 192.168.137.138 DHCP 344 DHCP ACK - Transaction ID 0xd354d95e
    5 8.251432 GarminIntern_42:20:dc Broadcast ARP 42 Who has 192.168.137.1? Tell 192.168.137.138
    6 8.251466 56:14:f3:f6:ab:85 GarminIntern_42:20:dc ARP 42 192.168.137.1 is at 56:14:f3:f6:ab:85
    7 8.253346 192.168.137.138 192.168.137.1 DNS 76 Standard query 0xa457 A clock.garmin.com
    8 8.378122 192.168.137.1 192.168.137.138 DNS 502 Standard query response 0xa457 A clock.garmin.com A 204.77.162.174 A 96.7.49.64 A 95.101.36.67 A 23.211.133.65 A 184.85.248.66 A 184.26.160.66 A 193.108.91.59 AAAA 2600:1408:1c::40 AAAA 2600:1480:4800::43 AAAA 2600:1401:1::41 AAAA 2a02:26f0:117::42 AAAA 2600:1480:f000::42

    after that stuck on this 
    reboot and restoring hotspot to default doesn't help