-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test ID.7 #336
Comments
Hey, I‘d rather prefer VW fixing this. For legacy cars it works charmingly with different users… |
Seems like VW is fixing this in some kind of way, they announced a "new experience" (rough translation below):
which translates to:
|
Yes, I've read this as well. Seems they listened to me ;-)) |
Is it fixed now? I think the change was rolled out. |
The change is in effect - but we did not really have the chance to test for differences. I'll post an amendment here as soon as I see a difference. |
OK, it seems that rather trivial data (odometer value and SOC) can be obtained by the main user also when a "guest user" is logged into the vehicle. However, no systematic difference discovered so far. |
Great work, the brand new ID.7 is now part of my FHEM smarthome.
Feature suggestion: Currently, a single user/password combination for the car is accepted. If different users operate the car, quite a few data items are not available in case the weconnect-mqtt login is under another user name.
It should be possible to provide credentials for different users, and then switch the weconnect-mqtt login according to the person currently operating the car.
Regards
pah
The text was updated successfully, but these errors were encountered: