Workaround for logout in the Xplora® App

[Ludy87]

1. add phone number from watch to contacts (as admin) As an admin user, add watches phone number to watches contacts Workaround for logout in the Xplora® App #24 (comment)
2. create a login profile for this phone number
3. log into the app with the created profile to test whether it works
4. use the login data for the integration

[FerretMonger]

When would I need to do this? I just got the watch and want to set the integration for the first time.

[Ludy87]

Use the Xplora app to find the contact's number as described above.

[mschiessl]

They only allow "2" administrators, which is me and my wife - so I cannot add the watch itself as an admin.
Any suggestions?
Should we raise a support on xplora side ?

[Ludy87]

@mschiessl create an account with your watch's phone number and include the number as a contact. The integration does not require an admin as a user.

[mschiessl]

Thanks, @Ludy87, makes total sense now!
I got the following sentence totally wrong:

add phone number from watch to contacts (as admin)

could be better:

As an admin user, add watches phone number to watches contacts

[PStenbumling]

@mschiessl create an account with your watch's phone number and include the number as a contact. The integration does not require an admin as a user.

How and where do you create an account?
from the mobile app i'm unable to get an verification, have added the xploras number to contacts.

[Ludy87]

1. Download the app Android or [Apple](https://apps.apple.com/ de/app/xplora/id1521983878).
2. You select the item "Create account"
3. Follow the instructions
4. Done

---

You are still logged into the app:

1. log out
2. You select the item "Create account"
3. Follow the instructions
4. Done

[sevorl]

I struggled with this manual at first. I found this manual very useful:
https://www.telekom.de/hilfe/mobilfunk-mobiles-internet/xplora-x5-play-esim-smartwatch/neue-gruppenmitglieder?samChecked=true

Maybe this is helpful for anyone else...

BTW: Excelent Work Ludy87!

[xeor]

I'm a little confused by this workaround..

• Is it needed only if you have problems that you are logged out, or is it always needed?
• Is the goal to have a dedicated login user for the API?
• What if you have multiple watches, will 1 watch be used for both numbers and need access to both?
• Will the phonenumber setting be the same as child_phonenumber?
• Will the kid have a "dummy" number (itself) on the watch?

Don't need answer to all of it, but something to shed some light on the confusion.. It seams to be multiple issues that have problems with login.

[Ludy87]

An admin/user/parent can only login on ONE device, either in the app on the mobile phone or in the integration. It is therefore necessary to create an app account on the mobile phone in order to be able to use an "extra" user for the integration.

phonenumber is the number from App/integration User, not from watch.

The watch usually has its own phone number, hence its own key 'child_phonenumber'
In itself, the watch has a unique ID ('watch_id')

xplora_watch/custom_components/xplora_watch/__init__.py

Line 135 in b97df72

_LOGGER.debug(f"Xplora® Watch IDs: {watchUserIDs}")

[xeor]

Does this trick work anymore? When logged in as a parent, I can see the watch have it's own phone-number as contact. I can also login using the same phone-number in the app and verify that it sees itself.

• 111: Phone-number for the simcard on the watch, using the same as was installed when bought
• 222: My own (parent) phone-number

I removed, password, timezone, userlang and country_code below in the configuration examples

# This gives `pyxplora_api.exception_classes.LoginError: Login to Xplora® API failed. Check your input! - 1`
xplora_watch:
  phonenumber: "111"
  child_phonenumber:
    - "111"

# This works, but throws me out from the app on the phone when home-assistant is starting
xplora_watch:
  phonenumber: "222"
  child_phonenumber:
    - "111"

I also tried "manually" using the code found in pyxplora_api.

# This works
gql.runGqlQuery(gql_mutations.SIGN_M.get("issueTokenM", ""), {'countryPhoneNumber': '+47', 'phoneNumber': '222', 'password': 'password-hash-here', 'userLang': 'nb-NO', 'timeZone': 'Europe/Oslo'})

# same with phoneNumber of watch gives
{'errors': [{'code': 'E000025', 'message': 'Incorrect password.'}], 'data': {'issueToken': None}}

I got E000025 on my own phone-number in the beginning as well, however, that all the sudden fixed itself after fiddling with resetting the password on the account (even tho I could login using the password I tried)..

Any tips?

[Ludy87]

@xeor Has a user account been created with the phone number from the watch?

[xeor]

@Ludy87 yes, I have created one from the xplora app and I can login using it. I see in it's profile-page that it has a dedicated mail-address as well. It can see the watch when logged in, but there is no information like location and such (since it's not a guardian?).

I have also tried to remove the 111 number from the contact-list and readd it using the qr code instead of adding it using guardian>add-contact. Both methods yields the same error..