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

Unable to update charging_profile warning since 2024.5.0 #116567

Closed
Gloomyeye opened this issue May 1, 2024 · 10 comments · Fixed by bimmerconnected/bimmer_connected#615 or #118179
Closed

Comments

@Gloomyeye
Copy link

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?

Logger: bimmer_connected.vehicle.vehicle
Quelle: components/bmw_connected_drive/coordinator.py:58
Erstmals aufgetreten: 22:13:20 (12 Vorkommnisse)
Zuletzt protokolliert: 23:08:29
Unable to update charging_profile - (TypeError) argument of type 'NoneType' is not iterable

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented May 1, 2024

Hey there @gerard33, @rikroe, mind taking a look at this issue as it has been labeled with an integration (bmw_connected_drive) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of bmw_connected_drive can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign bmw_connected_drive Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


bmw_connected_drive documentation
bmw_connected_drive source
(message by IssueLinks)

@luke7101
Copy link

luke7101 commented May 2, 2024

Same here

@rikroe
Copy link
Contributor

rikroe commented May 2, 2024

Do you have electric cars or combustion only?

@luke7101
Copy link

luke7101 commented May 2, 2024

Petrol car only for me 😁

@rikroe
Copy link
Contributor

rikroe commented May 2, 2024

Found the culprit, You can safely ignore this warning (if you're a petrolhead ;) ). I'll update the lib.

@Gloomyeye
Copy link
Author

Me, too. Only combustion.

@luke7101
Copy link

luke7101 commented May 6, 2024

Hi @rikroe, the logs are flooded by the error. Is there a way to avoid this, while waiting for the update ? Thanks

@rikroe
Copy link
Contributor

rikroe commented May 7, 2024

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.

@luke7101
Copy link

luke7101 commented May 7, 2024

Ok, no big deal. Thanks again

@luke7101
Copy link

Hi, just to let you know, v2024.5.4 here, error in log still present.

@github-actions github-actions bot locked and limited conversation to collaborators Jun 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants