No stable connection between ID.7 and VWsFriend / Trips are not recorded

[mailkluge]

I installed a couple of days ago the application VWsFriend and setup and configuration runs very well and I could very fast "see" my ID.7 Tourer in the status. After a view shorter trips (max. 45min) I notice, that the trips are not recorded or only partial. I could recognized too, that the web-applications runs stable but the status of the car is often not correct (missing charge icon if it is connected to a charging station). After restarting of the docker container that status is correct.

I assume that the connection to the VW Backend is not stable...is there any possibility to analyze this (LogFile?). Or is this a know problem?

I saw that there is another application still in development "Car Connectivity" is it more stable? Or can I try to change something?

Please give me a hint or advise what I can check to find the problem.

[kotipalvelu]

There might be some server side problems right now as trips are also not recorded on my ID.4, only charges are present in the database. This is new'ish issue, trips was recorded mostly OK until 18th of November. Breaks for (trip) data collection have happend couple of times during last 3-4 months though, but those breaks have been short only day or so and mostly full stops e.g. nothing was recorded.

[tillsteinbach]

Might be the same reason as #752

[mailkluge]

@tillsteinbach

With latest update, connection to weconnect is possible again. But stability is not good. It seams that it comes often to an error:

Normal behaviour:
vwsfriend-1 | 2025-12-01T05:47:35+0000:INFO:weconnect_mqtt_base:Update data from WeConnect
vwsfriend-1 | 2025-12-01T05:47:35+0000:INFO:weconnect:Server asks for new authorization
vwsfriend-1 | 2025-12-01T06:03:30+0000:INFO:weconnect_mqtt_base:Retrieval error during update. Will try again after configured interval of 300s
vwsfriend-1 | 2025-12-01T06:03:30+0000:WARNING:vwsfriend_base:Retrieval error during update. Will try again after configured interval of 300s
vwsfriend-1 | 2025-12-01T06:08:25+0000:INFO:weconnect_mqtt_base:Update data from WeConnect
vwsfriend-1 | 2025-12-01T06:08:25+0000:INFO:weconnect:Server asks for new authorization
vwsfriend-1 | 2025-12-01T06:08:26+0000:INFO:vw_web_session:[_get_login_form] OAuth callback URL found in Location header: weconnect://authenticated#access_token=xxxxx
vwsfriend-1 | 2025-12-01T06:08:27+0000:INFO:vw_web_session:Found custom scheme URL during initial auth page fetch
vwsfriend-1 | 2025-12-01T06:08:27+0000:INFO:vw_web_session:Reached final OAuth callback URL with tokens

This behavior repeats approximately every 1,5h.

But it breaks often like described here:
vwsfriend-1 | 2025-12-01T06:32:47+0000:INFO:weconnect:Server asks for new authorization
vwsfriend-1 | 2025-12-01T06:48:42+0000:INFO:weconnect_mqtt_base:Client successfully disconnected
vwsfriend-1 | Traceback (most recent call last):
vwsfriend-1 | File "/opt/venv/bin/vwsfriend", line 8, in
vwsfriend-1 | 2025-12-01T06:48:42+0000:ERROR:vwsfriend_base:MQTT Connection failed
vwsfriend-1 | sys.exit(main())
vwsfriend-1 | ^^^^^^
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/vwsfriend/vwsfriend_base.py", line 516, in main
vwsfriend-1 | mqttCLient.updateWeConnect(reraise=True)
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/weconnect_mqtt/weconnect_mqtt_base.py", line 462, in updateWeConnect
vwsfriend-1 | self.weConnect.update(updateCapabilities=self.updateCapabilities, updatePictures=self.updatePictures, selective=self.selective, force=True)
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/weconnect/weconnect.py", line 199, in update
vwsfriend-1 | self.updateComplete()
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/weconnect/addressable.py", line 533, in updateComplete
vwsfriend-1 | child.updateComplete()
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/weconnect/addressable.py", line 533, in updateComplete
vwsfriend-1 | child.updateComplete()
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/weconnect/addressable.py", line 533, in updateComplete
vwsfriend-1 | child.updateComplete()
vwsfriend-1 | [Previous line repeated 3 more times]
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/weconnect/addressable.py", line 96, in updateComplete
vwsfriend-1 | observer(element=self, flags=self.onCompleteNotifyFlags)
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/vwsfriend/agents/charge_agent.py", line 224, in _onChargingStateChange
vwsfriend-1 | self.updatePosition()
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/vwsfriend/agents/charge_agent.py", line 385, in updatePosition
vwsfriend-1 | self.chargingSession.charger = chargerFromLatLonWithGeofence(weConnect=self.vehicle.weConnectVehicle.weConnect, session=self.session,
vwsfriend-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/sqlalchemy/orm/attributes.py", line 540, in set
vwsfriend-1 | self.impl.set(
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/sqlalchemy/orm/attributes.py", line 1477, in set
vwsfriend-1 | value = self.fire_replace_event(state, dict, value, old, initiator)
vwsfriend-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/sqlalchemy/orm/attributes.py", line 1520, in fire_replace_event
vwsfriend-1 | state.modified_event(dict, self, previous)
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/sqlalchemy/orm/state.py", line 927, in _modified_event
vwsfriend-1 | session._autobegin_t()
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 1879, in _autobegin_t
vwsfriend-1 | trans = SessionTransaction(
vwsfriend-1 | ^^^^^^^^^^^^^^^^^^^
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 929, in init
vwsfriend-1 | TransactionalContext._trans_ctx_check(session)
vwsfriend-1 | File "/opt/venv/lib/python3.12/site-packages/sqlalchemy/engine/util.py", line 111, in _trans_ctx_check
vwsfriend-1 | raise exc.InvalidRequestError(
vwsfriend-1 | sqlalchemy.exc.InvalidRequestError: Can't operate on closed transaction inside context manager. Please complete the context manager before emitting further commands.

Can this be checked please and to find measures to make it more resilient?

I am absolutely open to test changes soon.