-
-
Notifications
You must be signed in to change notification settings - Fork 698
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
Vehicle can not connect anymore with 0.131.11 (vw ID family) #17715
Comments
Everything is fine here with ID.4 and 0.131.11. |
Can confirm with 0.131.9, “Ladebereit. Warte auf Fahrzeug”. MySkoda 1.15.3 integration for Home Assistant shows correct charging power. Edit: evcc shows neither charging power nor SoC, MySkoda HA shows both. |
Same for me with my ID.4 with 0.131.11 But I saw this issue with 0.131.6 too, where it was working well for a while. |
Right J0ergW. That's it! |
@timoglaess Please reconsider closing this issue. I've got no consent to agree to and it still does not work in evcc. Please note that MySkoda HA integration works. MySkoda HA integration will btw detect a missing consent and notify me accordingly, which it currently does not. |
Did a downgrade from evcc 0.131.9 to 0.131.8 and now everythings works again. |
Same here with evcc evcc 0.131.11. I logged in at Volkswagen add clicked the disclaimer but error persists. |
evcc restarted? |
Boring afternoon, tried something…
Issue resolved on my side. Running stable evcc on Debian 12 in a LXC container. PV access is via modbus-proxy, that’s why Home Assistant shows in the logs. Car is a Skoda Enyaq but that’s the same VW stuff anyway. Log excerpt from 0.131.9:
Log from 0.131.11:
|
Describe the bug
During config test in the vehicle configuration: "cannot create vehicle type 'template': cannot create vehicle type 'vw': missing state"
Steps to reproduce
...
Configuration details
configere via experimental console
Log details
What type of operating system are you running?
Linux
Nightly build
Version
evcc version 0.131.11
The text was updated successfully, but these errors were encountered: