Skip to content
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

Unsupported chargingScenario: initializationChargingCommunication #676

Open
akahl opened this issue Oct 12, 2024 · 2 comments
Open

Unsupported chargingScenario: initializationChargingCommunication #676

akahl opened this issue Oct 12, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@akahl
Copy link

akahl commented Oct 12, 2024

2024-10-05T15:14:40+0000:WARNING:addressable:/vehicles/<FIN>/domains/charging/chargingStatus/chargingScenario: An unsupported chargingScenario: initializationChargingCommunication was provided, known values are [off, immediatelyChargingActive, immediatelyChargingFinished, chargingToDepartureTimeWaiting, chargingToDepartureTimeActive, optimisedChargingFinished, errorChargingSystem, unknown charging scenario] please report this as a bug

@tillsteinbach tillsteinbach self-assigned this Nov 4, 2024
@tillsteinbach tillsteinbach added the enhancement New feature or request label Nov 4, 2024
@tillsteinbach
Copy link
Owner

Will be added to next release

@amenychtas
Copy link

I have the same issue with my ID.3 after the OTA update to v3.7.

WARNING:addressable:/vehicles/XXXXX/domains/charging/chargingStatus/chargingScenario: An unsupported chargingScenario: initializationChargingCommunication was provided, known values are [off, immediatelyChargingActive, immediatelyChargingFinished, chargingToDepartureTimeWaiting, chargingToDepartureTimeActive, optimisedChargingFinished, errorChargingSystem, unknown charging scenario] please report this as a bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants