xplora X6 Play - Charging state does not update

[Tommapika]

What version of Integration has the issue?

2.10.2

System Health details

System Information

version	core-2023.9.2
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.11.5
os_name	Linux
os_version	6.1.45
arch	x86_64
timezone	Europe/Oslo
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	5000
Installed Version	1.32.1
Stage	running
Available Repositories	1289
Downloaded Repositories	25

Home Assistant Cloud

logged_in	true
subscription_expiration	19 October 2023 at 02:00
relayer_connected	true
relayer_region	eu-central-1
remote_enabled	true
remote_connected	true
alexa_enabled	false
google_enabled	true
remote_server	eu-central-1-14.ui.nabu.casa
certificate_status	ready
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 10.5
update_channel	stable
supervisor_version	supervisor-2023.09.2
agent_version	1.5.1
docker_version	23.0.6
disk_total	30.8 GB
disk_used	5.0 GB
healthy	true
supported	true
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Terminal & SSH (9.7.1), Mosquitto broker (6.3.1), Studio Code Server (5.10.2)

Dashboards

dashboards	4
resources	18
views	7
mode	storage

Recorder

oldest_recorder_run	14 September 2023 at 15:42
current_recorder_run	22 September 2023 at 19:29
estimated_db_size	79.93 MiB
database_engine	sqlite
database_version	3.41.2

Checklist

• I have enabled debug logging for my installation.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).

Describe the issue

I have two X6 Play connected to HA and everything works, except the charging state.
Im new to HA but i'll try to explain.
The entity im talking about is "binary_sensor.max_watch_charging_pappa" and the equivalent for the other watch.
The account used in the integration is admin in the Xplora App.

In developer tools it shows the state "off", and when i open the entity itself it sais "Not charging". And this does not change if i charge the watches.
The only changes on the entity on the logbook is "Became unavailable" and "Turned off". But those changes does not seem to have any relation to when i plug or unplug the watches from the charger.

I dont know how the debugger works, put i turned it on and let it run while i charged and not charged the watches.

Reproduction steps

Debug logs

2023-09-24 12:01:54.793 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Fetch data from Xplora: 9493465
2023-09-24 12:01:57.210 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] load address from openstreetmap.org
2023-09-24 12:01:57.211 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Fetch data from Xplora: 9509753
2023-09-24 12:01:59.706 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] load address from openstreetmap.org
2023-09-24 12:01:59.709 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Manually updated xplora_watch-552 data
2023-09-24 12:01:59.714 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Finished fetching xplora_watch-552 data in 6.757 seconds (success: True)
2023-09-24 12:08:00.851 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Fetch data from Xplora: 9493465
2023-09-24 12:08:03.499 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] load address from openstreetmap.org
2023-09-24 12:08:03.502 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Fetch data from Xplora: 9509753
2023-09-24 12:08:05.956 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] load address from openstreetmap.org
2023-09-24 12:08:05.958 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Manually updated xplora_watch-552 data
2023-09-24 12:08:05.963 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Finished fetching xplora_watch-552 data in 7.005 seconds (success: True)
2023-09-24 12:14:07.806 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Fetch data from Xplora: 9493465
2023-09-24 12:14:10.314 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] load address from openstreetmap.org
2023-09-24 12:14:10.317 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Fetch data from Xplora: 9509753
2023-09-24 12:14:12.802 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] load address from openstreetmap.org
2023-09-24 12:14:12.805 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Manually updated xplora_watch-552 data
2023-09-24 12:14:12.810 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Finished fetching xplora_watch-552 data in 6.852 seconds (success: True)
2023-09-24 12:20:13.955 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Fetch data from Xplora: 9493465
2023-09-24 12:20:16.440 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] load address from openstreetmap.org
2023-09-24 12:20:16.443 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Fetch data from Xplora: 9509753
2023-09-24 12:20:18.961 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] load address from openstreetmap.org
2023-09-24 12:20:18.964 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Manually updated xplora_watch-552 data
2023-09-24 12:20:18.968 DEBUG (MainThread) [custom_components.xplora_watch.coordinator] Finished fetching xplora_watch-552 data in 7.011 seconds (success: True)

[github-actions]

👋 @Tommapika, it is checked whether there is a bug. Please have some patience.
This action was performed automatically.

[Ludy87]

The update only takes place when the corresponding update time specified during setup has passed.

[Tommapika]

The update only takes place when the corresponding update time specified during setup has passed.

Do you mean the scan intervall? The state doesnt change no mater how long i wait.

[github-actions]

👋 @Tommapika, we found the bug, it will be fixed shortly.
This action was performed automatically.

[Ludy87]

Apparently there are problems with Xplora, I have two identical clocks, one is updated and the other unfortunately not. Messages are synchronous. Can you test this on yourself?

[Tommapika]

i have the same problem with both watches. Everything is updateing, the battery percentage and location, but not the charging state.

[Ludy87]

is it displayed correctly in the app?

[Tommapika]

In the Xplora app? It does not show it charging there either, it looks like.... Is it suppose to?

[Ludy87]

I now assume that there is an error in Xplora. I'm sorry, I can't help with this, you should write to support, which I already did and didn't get an answer.

[github-actions]

🐛 The problem is with Xplora®, please contact support.
This action was performed automatically.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

[Ludy87]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.