Upcoming API changes notification from BMW

[cbjoldham]

The problem

This is a heads up from the maintainers of the BMW Connected Drive integration.

In the last 48 hours I have:

• received a notification via the BMW Android App of upcoming API changes for charge control
• had several authentication issues in the Home Assistant integration
• had an app update from my electricity supplier that forced a reintegration through a new flow with BMW

The need to reauthenticate the integration in Home Assistant is not the issue I am reporting, these are just likely symptoms of disruption of the API backend. To date I have always been able to reauthenticate.

I will attach a screenshot of the notification from the BMW app, it leads to the following link

https://faq-backend.api.bmw/uk/s/article/Which-electricity-providers-can-charge-my-BMW-via-remote-access-ZwUkP

Apologies I did not immediately realise the significance of the new integration flow from my electricity provider, as it was advertised as a change from them, so I did not record it in any way. However in retrospect it was clearly hosted by BMW not them.

For additional context I am in the Rest of World region in this integration's terms - so Europe not China/North America

What version of Home Assistant Core has the issue?

core-2024.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

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

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

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)}}

[helmerzNL]

Next to this change in Remote Control Charging, it also mentions that you cannon control your car anymore with a Home Automation system (like Home Assistant). (in the Dutch notification Home Automatisering (a.k.a. Home Automation) was mentioned explicitely, a bit more explicitely the in the English screenshot)

Any idee on how to proceed? I haven’t been able to get the BMW integration working for months now :-(

[gigatexel]

So, again, out of the blue, things will get crippled by a manufacturer. Rip bmw integration.

[Trojafux]

Are you sure, that no access via API will be possible any longer? Or just the charging features? My hope is that there will always be an API since there is an Amazon Alexa skill that also needs to gain access.

[sshaikh]

Hitting reauthentication issues here. Not sure if related but posting for the data point.

[JjyKs]

Just got failed auth and now the plugin fails to relogin, thank you BMW for ruining a perfectly good API without even providing an alternative ways to handle things that it enabled.

[mahi2003]

So far my vehicles are still online in Home Assistant - no re-authentication required, but I did notice the connection was down a lot today. Maybe they are simply having server problems? Fingers crossed...

[JjyKs]

Let's hope so, I think that the original deadline was on 1.9.2025, so maybe they're getting the servers ready for transition.

[Trojafux]

Having repeated re-authentication required issues here aswell. I see a new type of error message:

Logger: bimmer_connected.api.client
Source: components/bmw_connected_drive/coordinator.py:74
First occurred: August 19, 2025 at 5:22:42 PM (16 occurrences)
Last logged: 2:29:17 PM

MyBMWQuotaError due to HTTPStatusError: { "statusCode": 403, "message": "Out of call volume quota. Quota will be replenished in 00:49:03." }
MyBMWQuotaError due to HTTPStatusError: { "statusCode": 403, "message": "Out of call volume quota. Quota will be replenished in 00:13:43." }
MyBMWQuotaError due to HTTPStatusError: { "statusCode": 403, "message": "Out of call volume quota. Quota will be replenished in 00:03:41." }
MyBMWQuotaError due to HTTPStatusError: { "statusCode": 403, "message": "Out of call volume quota. Quota will be replenished in 00:33:21." }
MyBMWQuotaError due to HTTPStatusError: { "statusCode": 403, "message": "Out of call volume quota. Quota will be replenished in 00:30:43." }

[JjyKs]

I was digging as well and noticed the same. Managed to reauthenticate after the timeout but got kicked out after couple syncs.

Maybe lowering the default polling rate would help?

Having repeated re-authentication required issues here aswell. I see a new type of error message:

Logger: bimmer_connected.api.client Source: components/bmw_connected_drive/coordinator.py:74 First occurred: August 19, 2025 at 5:22:42 PM (16 occurrences) Last logged: 2:29:17 PM

MyBMWQuotaError due to HTTPStatusError: { "statusCode": 403, "message": "Out of call volume quota. Quota will be replenished in 00:49:03." } MyBMWQuotaError due to HTTPStatusError: { "statusCode": 403, "message": "Out of call volume quota. Quota will be replenished in 00:13:43." } MyBMWQuotaError due to HTTPStatusError: { "statusCode": 403, "message": "Out of call volume quota. Quota will be replenished in 00:03:41." } MyBMWQuotaError due to HTTPStatusError: { "statusCode": 403, "message": "Out of call volume quota. Quota will be replenished in 00:33:21." } MyBMWQuotaError due to HTTPStatusError: { "statusCode": 403, "message": "Out of call volume quota. Quota will be replenished in 00:30:43." }

[mahi2003]

I just checked my logs and see the same errors. That explains the frequent downtime today.