BMW ConnectedDrive component

Hi, is there any solution for executionStatus errors? I noticed there is a closed issue in github with recent update without reply (basically the same config as the last post, even the error details, except my car is G05).
I get this error as well everytime i try to execute something. But despite the error, the calls soon or later works.

Hi,

I’ve got 530e and it would be great if there was a service for starting immediate charging. Problem is that I would like to heat up the cabin before driving but it takes so much power that it reduces the electric range for about 10km (range is not that good during winter anyway). If it was possible to call a service that starts the charging immediately, the power used during the heat up would come from the connected charger and not from the battery. Unfortunately, due to a bad design I would say, it seems that BMW does not start the charging without a trigger even if the battery level goes down due to heating.

With this service I could trigger the charging automatically always when heating is started. Any change to get this service included in this component? Would try to implement it myself but I have no experience on Python and I understood nothing by looking at the code… This service should be possible to implement though as it is available in the BMW app (which is horrible btw).

Can you make a FR here -> https://github.com/bimmerconnected/bimmer_connected/issues/new?assignees=&labels=&template=feature_request.md
And please share some screenshots of the app with the immediate charging service.

I did that, thanks!

Is there anything i can do to solve the executionStatus issue? :slight_smile:

I need to correct my previous message. I did more research and it actually seems that charging is started when heating starts eating the battery. But I suspect the charging mode needs to be ”immediate” in this case.

Still it would be nice to see this feature in HA! I saw some work done on getting data of all trips out of the car (consumptions, speed, etc). This is something that even the BMW app cannot do, so that wouldnt it be awesome to have something like that?!

Hi,

I upgraded my car and I’m trying to get the connecteddrive component to deal with the change. I had an i3 and now I have a newer i3.

It didn’t seem to pick up my connecteddrive changes. So I removed the config from configuration.yaml, restarted, removed all the entities that now were unavailable. Then I put the config back and restarted again.

This picked up the car, but all the entities were named like “binary_sensor.i3s_120_charging_status”. I just want plain “i3”, not “i3s_120”.

Can I control this? I put into known_devices :

i3s_120:
  icon: mdi:car
  mac:
  name: i3
  picture:
  track: true

However I’m not sure where this “name” pulls through to. Certainly didn’t change the entity names.

What I’m particularly about is to have Alexa see it as “i3”. Right now Alexa has “i3s 120” which doesn’t exactly roll off the tongue…

I can manually rename in the Alexa app but its quite a lot of devices.

Thanks for hints and advice!

Steve

The integration uses the car model from the BMW ConnectedDrive API. Your new i3 is called i3s_120 there, so that name is used in the entity ids.
You can change the entity ids (e.g. binary_sensor.i3s_120_charging_status) by clicking on the entity and then in the popup window on the cog in the upper right corner. Then you can rename the entity id there to binary_sensor.i3_charging_status.
For use with Alexa though it is not necessary to rename the entity id, just renaming the entity name should work. You can do this in the same popup window.

Only the device tracker is controlled in known_devices.yaml.

1 Like

Anyone else getting Authentication Errors from the integration today?
My password hasn’t changed and the BMW App on my phone still works…

No error for me

Yep, same for me.

I am getting the same error.

Confirmed. Rebooted earlier and I’m getting authentication errors. Able to log into connected drive on the website OK.

Logger: bimmer_connected.account
Source: /usr/local/lib/python3.8/site-packages/bimmer_connected/account.py:115
First occurred: 12:41:37 (1 occurrences)
Last logged: 12:41:37

Authentication failed. Maybe your password is invalid?

Same here. I actually did something to my secrets.yaml right before the reboot, but reverting to the “old” secrets.yaml did not help either. Error stays the same after each reboot

Same here!

Same here! Does anyone know what can happen?

I made an issue: https://github.com/home-assistant/core/issues/42139

Yes! Same error for me. App works but HA does not.

same here
there is already a issue open for that

Same here. And the same issue with Audi