MQTT drops parking position

[mattsve]

After a while MQTT often drops parking/parkingPosition/longitude and parking/parkingPosition/latitude after a while (today after 15 hours) making home assistant marking the car not having a position . VWs app and vwsfriend shows the car as parked and
weconnect/rawjson has parking.parkingPosition set.

Ideas why? What can I do to help with troubleshooting?

[tillsteinbach]

Hmm, I will try to reproduce that. So far I have not experienced that.

[HenrikPPersson]

I don't know if this is related, but most trips are not registered in the database when running in MQTT mode. The PK (id) is incremented the (seemingly) correct number of times, but only some random trips are actually stored in the database.

[milvert]

I have the same issue. How can I help to debug this?

Should I disable mqtt within vwsfriend and just run vwsfriend-mqtt to see if it appears there as well?

[tillsteinbach]

That would be interesting, yes

[wormiedk]

On my installation parking position is only updated when restarting the docker containers

[milvert]

I have been running a separate Dockercontainer for some time now but the only error is this:

2024-02-26T18:06:59+0100:INFO:weconnect_mqtt_base:Update data from WeConnect
2024-02-26T18:07:02+0100:WARNING:timer:/vehicles/my_vw/domains/automation/climatisationTimer/timers/1/recurringTimer: Unknown attribute targetTime with value 06:40
2024-02-26T18:07:02+0100:WARNING:timer:/vehicles/my_vw/domains/automation/climatisationTimer/timers/1/recurringTimer: Unknown attribute repetitionDays with value ['wednesday']
2024-02-26T18:07:02+0100:WARNING:timer:/vehicles/my_vw/domains/automation/climatisationTimer/timers/2/recurringTimer: Unknown attribute targetTime with value 14:00
2024-02-26T18:07:02+0100:WARNING:timer:/vehicles/my_vw/domains/automation/climatisationTimer/timers/2/recurringTimer: Unknown attribute repetitionDays with value ['tuesday']
2024-02-26T18:07:02+0100:WARNING:generic_status:/vehicles/my_vw/domains/automation/chargingProfiles: Unknown attribute nextChargingTimer with value {'id': 0, 'targetSOCreachable': 'invalid'}
2024-02-26T18:07:02+0100:WARNING:generic_status:/vehicles/my_vw/domains/chargingProfiles/chargingProfilesStatus: Unknown attribute nextChargingTimer with value {'id': 0, 'targetSOCreachable': 'invalid'}
2024-02-26T18:07:02+0100:WARNING:timer:/vehicles/my_vw/domains/climatisationTimers/climatisationTimersStatus/timers/1/recurringTimer: Unknown attribute targetTime with value 06:40
2024-02-26T18:07:02+0100:WARNING:timer:/vehicles/my_vw/domains/climatisationTimers/climatisationTimersStatus/timers/1/recurringTimer: Unknown attribute repetitionDays with value ['wednesday']
2024-02-26T18:07:02+0100:WARNING:timer:/vehicles/my_vw/domains/climatisationTimers/climatisationTimersStatus/timers/2/recurringTimer: Unknown attribute targetTime with value 14:00
2024-02-26T18:07:02+0100:WARNING:timer:/vehicles/my_vw/domains/climatisationTimers/climatisationTimersStatus/timers/2/recurringTimer: Unknown attribute repetitionDays with value ['tuesday']

but since a couple of days the WeConnect shows
Parking position (From 2024-02-21T19:41:16+00:00)

so it seems something is wierd with parking.

After a restart of the DockerContainer the parking position works again.

@tillsteinbach Whats the easiest way to debug the API from vw to see what I recieves?