[BUG] The format of the GPS coordinates seems to be different from the previous version

[Spartacus68]

Before you post a new issue - you must first check the following (and check the boxes with an "X" below)

• [x ] 1.) Can you login using the smartphone app We Connect (not We Connect ID or We Connect GO) and interact with your car?
• [ ] 2.) Please make sure that you can login into https://vwid.vwgroup.io/ and make sure that any "Terms and Conditions" are all checked
• [ x] 3.) I do not have MFA enabled.

Environment

• Volkswagencarnet release with the issue:
• Last working homeassistant-volkswagencarnet release (if known):
• Home Assistant Core release with the issue:
• Operating environment (Home Assistant OS/Supervised/Container/Core/venv):
• Car model and year:
• Country where the car was bought:
• Valid We Connect subscription:
• Have you verified that the We Connect service works via VW´s portal?:

Describe the bug

seems to be that something has changed how GPS Data will be provided? since the update from yesterday I cannot use the places integration. Places for Cupra integration is still working ## Steps to Reproduce

Expected behavior

Screenshots

Traceback/Error logs

Debug information - all JSON responses from logfile

Additional context

[Spartacus68]

additional: I get this errors in places for the WE Integration:

2024-02-26 18:07:49.553 INFO (SyncWorker_21) [custom_components.places.sensor] (Golf) Starting Scan Interval Update (Tracked Entity: device_tracker.golf_position)
2024-02-26 18:07:49.553 WARNING (SyncWorker_21) [custom_components.places.sensor] (Golf) Tracked Entity (device_tracker.golf_position) Latitude/Longitude is not set or is not a number. Not Proceeding with Update.
2024-02-26 18:07:49.553 DEBUG (SyncWorker_21) [custom_components.places.sensor] (Golf) Tracked Entity (device_tracker.golf_position) details: <state device_tracker.golf_position=unknown; source_type=gps, model=Golf/None, last_updated=Unknown, assumed_state=True, icon=mdi:car, friendly_name=Golf Position @ 2024-02-26T18:02:09.185363+01:00>

the format of longitude and latitude seems to be different

[stickpin]

@Spartacus68 There were no changes in the device tracking for the last two months. 2024-02-26 18:07:49.553 INFO (SyncWorker_21) [custom_components.places.sensor] (Golf) Starting Scan Interval Update (Tracked Entity: device_tracker.golf_position) The warning that you see is coming from this integration: https://github.com/custom-components/places not from VW WE Connect.

[Spartacus68]

I know, this is from places integration! The error only occurs for the WeConnect Device all other Devices are still working. And this happens after the update yesterday. I removed places and WeConnect and installed it again. Same issue. Cupra and Handy DeviceTracker are working, WeConnect not. Something has changed Is it possibe to switch back to the old Version of WeConnect?

[Spartacus68]

maybe you can try to install the places integration and check, if weconnect is running correctly. For me it is not working anymore.

[stickpin]

What is the status of the parking position API?

What do you see in the attributes of the position sensor?

[Spartacus68]

Hi, yes I have this data also in the Frontend, but it will not transfered correctly to places? Seems to be somtheing wrong with the interface between the two applications. Maybe you can try to install the integration, and if it´s working with yours, then something is wrong with my HA. But as I said, it runs until yesterday with WeConnect and Cupra integration. I do not have an idea

[stickpin]

Sorry, I am not providing support to places. If data is present and visible in HA, you can check with the places developers.

[Spartacus68]

ok, then please tell me, how I can switch to the old version of WeConnect.

[stickpin]

A bit of googling will lead you to this page: https://hacs.xyz/docs/faq/select_version/

[Spartacus68]

Many thanks for that,

I switched back to the old version of WeConnect, and now "places" is working again! Seems to be that I have to decide whether I can use "places" or the auxiliary heater!

So, if you ask me, there are changes in how GPS Data will be transfered to HA. Maybe you can double-check it and let me know, iRegards, Christian

[stickpin]

@Spartacus68 please see this one: https://github.com/custom-components/places/issues/260

Uncheck GPS accuracy and it will work for you:

As I've mentioned before, the GPS accuracy is always 0, so I have no clue why it was working for you before.

[Spartacus68]

Hi,

I have checked it out, and it is not working with the new version. But it is true, if I switch on the GPS Acc. in the old version, it is also not working. If I switch it of again, then it works. With the new version of Weconnect it never works, with or without Acc.

I will remove both integrations now and will re-install. If it is working for you, there must be something wrong with my HA. I have also a fresh HA in a VM. I will setup WeConnect and places and let you know!

Thanks for support! Spartacus

[Spartacus68]

Hi,

so I have installed the two integrations on the new HA, running on my Qnap. And you´re right it is working! I do not unterstand, why it is not working on my prod system and why the old version is running and the new one not. It seems that I have to set up HA again. I think you can clos this topic. Thanks for support.

[stickpin]

@Spartacus68 thanks for reporting back. :) Try to uninstall both integrations on your prod system, restart HA, and install them once again. Sometimes it cleans some internal caches and starts to work again.