I notice that the connecteddrive maxFuel sensor doesn’t have a unit of measurement assigned – there’s no little label at the bottom of the circle like other numeric sensors do.
I also notice that it’s returning a value of 8. Now at integer precision, my i3 has a fuel capacity of 2 gallons – so that 8 is 8 liters.
So the component should report units for the maxFuel sensor and perform unit conversion when appropriate.
OK, it’s been a month and a half since I wondered if m1n3rva was still active and available for the bimmer_connected library which this component relies on. Has anyone heard from him/her in the meantime? Of course anyone can lose interest in a project or just become so swamped with paid work or personal issues that they just have to lay back for a while. That’s perfectly understandable. But does anyone else have the keys to the project? I’ve submitted a fix for the OPEN_TILT bug but with no one to accept the pull request nothing happens, right?
Figured this out. Turns out my 2016 X5 unlike my 2014 had an option in iDrive to enable / disable GPS tracking. If GPS Tracking is Disabled you will get the above error.
Not that it matters, but I think that sensor ‘charging_level_hv’ should have units “%” . . . since it’s a percentage of full charge. It would also make it easier to pick it out in the veritable garden of blooming sensors.
I am not sure how the name: parameter is determined, but i found for my car “330i” worked but “bmw” did not. This is important, as entities with names starting with numbers are handled differently. See:
In my case, I found this did not work:
data:
message: "{{ states.sensor.330i_remaining_range_fuel.state }} km"
Whereas this did:
data:
message: "{{ states.sensor['330i_remaining_range_fuel'].state }} km"
What are the rules on the name: parameter in the setup?
For the naming of the entities the name from the config is not used, but the type of car is used which is delivered by the bimmer_connected library.
When that type starts with an number, you indeed have to take the above into consideration, but that’s a HA thingy and not something this component can change.
You can however change the BMW entity names easily by just clicking on the cog when you have opened a entity.
Anyone heard anything about progress on the sunroof OPEN_TILT bug? Whenever I’ve got the sunroof popped open, I get a log full of critical component errors. Can anyone other than m1n3rva approve my pull request on github?
changed my car today
but hass still tries to get information of the old even if this is not longer in bmw connted drive
how to get hass to get the information about the new car?
I’ve already restarted hass but no change so far
solved it. had to use a new name for the new car. now it’s working
Has anyone heard anything about the whereabouts of m1n3rva (the maintainer of the bimmer_connected library that supports this component)? I’m bumping this because I’d asked four months ago if he/she had retired from the project, perhaps no longer has a BMW, maybe unavailable for other reasons . . . There are some outstanding issues to be solved and certainly other things will come up as time passes. Is there a succession plan? How does that work on github?
Locking doesn’t seem to be working and the state isn’t detected from the component and there’s a lot of 500 errors at the moment, is this just me or a general issue?
It’s not happening to me – what region are you in? And what kind of errors are you seeing? BMW has multiple regional servers.
I’ve been seeing this for several days in the UK. A server restart seems to get it working but with quite a lot of 500 errors
I got no update from @m1n3rva as well after the issues from a few months ago.
What you can try in the meanwhile to see if your PR fixes the open_tilt issue is adding the component as custom component to your HA.
In the manifest.json you can replace
"requirements": [
"bimmer_connected==0.5.3"
]
with
"requirements": [
"https://github.com/robthebold/bimmer_connected/archive/master.zip#bimmer_connected==0.5.5"
]
You have to make a release on your Github first with v0.5.5. I am not sure if referring to your Github like this works with manifest.json, but it used to work when the requirements where part of the py file so you can give it a shot.
Well regarding a custom component, after a little looking around got me to the “Development” section of the HA documentation, I didn’t get past the 2nd paragraph: “Before you start, make sure that you have read up on the Home Assistant architecture so that you are familiar with the concepts that make up Home Assistant.”
I’m afraid that learning a project’s architecture to make a one-liner code change isn’t very good ROI given my finite time on this mortal coil and the other demands life has of me.
I have managed to test the bimmer_connected library itself from the command line, and now I can confirm the addition of OPEN_TILT to the LidState Enums no longer causes account.update_vehicle_states to throw an error when the sunroof is tilted open.
I’ve had lots of issues recently, 99 times out of a 100 it will fail with the following
I see there was an earlier comment about Error 500 in the UK (where I live).
No worries, you don’t have to make the custom component your self 
Just do the following:
config\custom_components\bmw_connected_drive of your HA installation.bimmer_connected library with version 0.5.5.requirements part in manifest.json as mentioned in the post above.That should be all. No need to get into the Development section of HA 
Give it a try and definitely when your changes will solve the error when the sunroof is opened.
Sign in to your Connected Drive account on https://www.bmw-connecteddrive.se/app/index.html#/portal and accept the updated terms, and it will start working again in Home Assistant.