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

adding second user will stop syncing to Connect

Hi,

has anyone else had such problem that when Index has only one user (owner) profile in the scale, it works fine. Results are synced correctly to profile (>>>>>>>>>> V)

As soon as I add second user, then it does not sync anymore at all for both user. Just shows >>>>>>>>>> X for both. As soon as I remove second user, it starts work for me (owner) again.

So far I have:

reseted device several times

added second user via app and via web

changed any imaginable parameter on second user to see if any of them (height, birthday, activity class, etc) might be causing this

0 olni65 over 5 years ago

At one point in time - when they introduced GDPR - there was an issue that if one user on the scale hadn't given the GDPR consent nothing would work. Have person two given his/her consent?

0 raintz over 5 years ago in reply to olni65

When i invited new user, we finished set up on second users Connect account. So adding details like height and birthday etc. I doubled checked second user Profile and account but couldn't not fine location that would indicate GDPR consent option. Is it somewhere hidden on the users account?

0 olni65 over 5 years ago in reply to raintz

I don't remember exactly how it was done, but this forum post should explain it

forums.garmin.com/.../escalation---additional-index-users-unable-to-sync

0 olni65 over 5 years ago in reply to olni65

And here was an even more recent and perhaps better explanation, which you've probably seen since it's in the same forum and next post in line!! :-)

forums.garmin.com/.../garmin-scale-does-not-sync-guests

0 raintz over 5 years ago in reply to olni65

yep, that did the trick. My problem was that on we did not use app for second user and this option was not visible on web profile. But after downloading the app and following the steps on the link, both users data has been uploaded correctly to server.

Solved. Thanks for the help.