-
-
Notifications
You must be signed in to change notification settings - Fork 32.7k
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
Unable to update charging_profile warning since 2024.5.0 #116567
Unable to update charging_profile warning since 2024.5.0 #116567
Comments
Hey there @gerard33, @rikroe, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) bmw_connected_drive documentation |
Same here |
Do you have electric cars or combustion only? |
Petrol car only for me 😁 |
Found the culprit, You can safely ignore this warning (if you're a petrolhead ;) ). I'll update the lib. |
Me, too. Only combustion. |
Hi @rikroe, the logs are flooded by the error. Is there a way to avoid this, while waiting for the update ? Thanks |
Unfortunately you'll have to wait another week. I have done the changes but forgot to push them before going on vacation and got only my phone with me. |
Ok, no big deal. Thanks again |
Hi, just to let you know, v2024.5.4 here, error in log still present. |
The problem
Hello,
the newest version of home assistant creates a warning "Unable to update charging_profile" during start up of home assistant.
What version of Home Assistant Core has the issue?
core-2024.5.0
What was the last working version of Home Assistant Core?
core-2024.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
bmw_connected_drive
Link to integration documentation on our website
https://www.home-assistant.io/integrations/bmw_connected_drive/
Diagnostics information
config_entry-bmw_connected_drive-c80657dbc726e4d7e9dca3897d63bd81.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: