What does that mean? What is the latest beta? I’m on v.0.2.0 and there don’t seem to be any betas available.
I constantly get loads of warnings from this VW integration (10245 times in under 24 hours)
2024-01-16 10:45:32.817 WARNING (SyncWorker_16) [weconnect] /vehicles/WVWZZZE1ZMP051650/domains/automation/climatisationTimer/timers/1/singleTimer: Unknown attribute targetDateTime with value 2000-01-01T00:00:00Z
2024-01-16 10:45:32.817 WARNING (SyncWorker_16) [weconnect] /vehicles/WVWZZZE1ZMP051650/domains/automation/climatisationTimer/timers/2/singleTimer: Unknown attribute targetDateTime with value 2000-01-01T00:00:00Z
2024-01-16 10:45:32.818 WARNING (SyncWorker_16) [weconnect] /vehicles/WVWZZZE1ZMP051650/domains/automation/chargingProfiles: Unknown attribute nextChargingTimer with value {'id': 0, 'targetSOCreachable': 'calculating'}
2024-01-16 10:45:32.821 WARNING (SyncWorker_16) [weconnect] /vehicles/WVWZZZE1ZMP051650/domains/chargingProfiles/chargingProfilesStatus: Unknown attribute nextChargingTimer with value {'id': 0, 'targetSOCreachable': 'calculating'}
2024-01-16 10:45:32.821 WARNING (SyncWorker_16) [weconnect] /vehicles/WVWZZZE1ZMP051650/domains/climatisationTimers/climatisationTimersStatus/timers/1/singleTimer: Unknown attribute targetDateTime with value 2000-01-01T00:00:00Z
2024-01-16 10:45:32.821 WARNING (SyncWorker_16) [weconnect] /vehicles/WVWZZZE1ZMP051650/domains/climatisationTimers/climatisationTimersStatus/timers/2/singleTimer: Unknown attribute targetDateTime with value 2000-01-01T00:00:00Z
Can I stop this?
Also could it be the cause of my the invalid authentications I’m getting which appeared right in the middle of a ton of these warnings?
(192.168.1.25 is my HA server)
Sorry my bad, the plugins got confusing here, since there is also one called: Volkswagen We Connect
Where there is a new beta that fixed that issue that occured with the latest HA release. But if you use the VWC ID plugin there isn’t yet indeed.
Hello,
I’m trying to create an automation to remind me to lock the car if it’s idle and unlocked for too long.
I can see the history of the lock status entity shows what I need to trigger the automation, but when I try to set the trigger to be the unlocked state I’m only given the unavailable and unknown options.
Any ideas why this might be?
Cheers all
You can’t lock and unlock your ID remotely. Can’t even do that in the VW app!
That’s ok, I just want a notification after some time if I’ve forgotten to lock it, not to have it lock itself.
I’m kind of surprised that it’s not possible to do for the ID cars. Since I can do it with the VW app (and HA) for my Passat GTE, so I’d assume that for the full electric ID’s that are even newer it should be possible as well.
I have an automation for that, it is triggered when the state of “Door Lock Status” changes to “unlocked” for 5 minutes.
If you don’t get “unlocked” in the UI, then this state has not been recorded before, so you may have to set it it manually in the YAML code, mine looks like this:
alias: "Car not locked!"
description: ""
trigger:
- platform: state
entity_id:
- sensor.car_door_lock_status
to: unlocked
for:
hours: 0
minutes: 5
seconds: 0
condition: []
action:
- service: notify.pushover
data:
message: Car unlocked!
mode: single
@Aphotrax, I completely agree, they should be able to, and i am hoping that it would be possible with a future software update for the car. Currently I can start and stop charging as well as turn on and off the climatisation. So locking and unlocking should not be that difficult!
Hi,
I am getting many of those errors, and cannot access any property at all. I just updated via HACS to 0.2.0, but this doesn’t help. Looks like this is at least for a 2+ weeks.
Any help in resolving this would be appreciated.
Rainer
2024-01-29 17:48:21.308 WARNING (SyncWorker_2) [weconnect] An unsupported status: 1014 was provided, please report this as a bug
2024-01-29 17:48:21.308 WARNING (SyncWorker_2) [weconnect] An unsupported status: 1018 was provided, please report this as a bug
2024-01-29 17:48:21.308 WARNING (SyncWorker_2) [weconnect] An unsupported status: 1014 was provided, please report this as a bug
2024-01-29 17:48:21.309 WARNING (SyncWorker_2) [weconnect] An unsupported status: 1014 was provided, please report this as a bug
2024-01-29 17:48:21.309 WARNING (SyncWorker_2) [weconnect] An unsupported status: 1014 was provided, please report this as a bug
2024-01-29 17:48:21.309 WARNING (SyncWorker_2) [weconnect] An unsupported status: 1014 was provided, please report this as a bug
2024-01-29 17:48:21.310 WARNING (SyncWorker_2) [weconnect] An unsupported status: 1014 was provided, please report this as a bug
2024-01-29 17:48:21.310 WARNING (SyncWorker_2) [weconnect] An unsupported status: 1014 was provided, please report this as a bug
2024-01-29 17:48:21.771 WARNING (SyncWorker_2) [weconnect] /vehicles/WVWZxxxxxxx/domains/automation/climatisationTimer/timers/1/singleTimer: Unknown attribute targetDateTime with value 1999-12-31T23:00:00Z
this is really helpful, thankyou. will test it out this week
1 Like
Is there any suggestion about how I could re-ebnable the integration to working state? Or is it currently defunct?
It is not defunct - the problem is most likely related to either your VW account or your set up.
ok - I doubt it, because the error message claims “file a bug report”, but I’ll deinstall and try to reinstall. Keep in mind that it worked until these new errors popped up.
Rainer
In case anyone is interested, the Carplay version for HA is now available for those users using iphones. Just make sure you have the latest version of the companion app and version of iOS.
1 Like
I don’t know what happend, but out of the sudden it works again after a couple of weeks (yes, I did many restarts in between). Anyhow 
FYI, there are a number of open PR’s that aren’t merged yet into this library.
If you want to try them out, you can follow these steps after removing the current custom component.
Please note to change some things below if needed.
# SSH into Home Assistant and go to the config directory
$ ssh root@hass
# Go to the config directory
$ cd config
# Create a directory to keep the checked out repository
$ mkdir custom_components.git && cd custom_components.git
# Checkout the repository here
$ git clone https://github.com/mitch-dc/volkswagen_we_connect_id.git
# Create a new branch where we will combine multiple pull requests.
$ git switch -c integration main
# You can use this comment to pull and merge various PR's
$ git fetch origin pull/243/head:refs/heads/pr243 && git merge --no-edit pr243
Modify the last line to match the PR you want. I’ve merged 204, 243, 245, 246, 247 and 248. Some PR’s had a conflict you’ll need to fix. git will indicate what file has a conflict. Fix the file and confirm with git add <filename> && git commit.
Please don’t do that.
1 Like
What do you mean? I wanted to try this integration, but I couldn’t since I had to combine a few open MR’s. Even now, #204 is still open.
This could help out others who also want to try this integration, no?