BMW ConnectedDrive Binding

Hi, I am using 3.1.0. Do you have a fixed jar as well ? Thanks, Lars

Same here - i am also using stable 3.1.0 and got for a while now:

 **COMMUNICATION_ERROR**
Bad Request

In the logs:

13:20:44.931 [WARN ] [b.core.thing.binding.BaseThingHandler] - Handler VehicleHandler tried updating the thing status although the handler was already disposed.

I’ve got the same error “Bad Request” with the newest plugin and OH 2.5.9

Any news / updates to this?

Pull request was merged yesterday so changes will be in next milestone.

1 Like

I had this problem too - there was a major change between OH 3.0 and OH 3.1. Running now OH 3.1 with the bundle prepared for 3.2 without problems. Please check the latest release candidate from the links of the top post.

1 Like

@Lars_Deutsch @e36Alex @Benedikt_Penner
Please check the latest release candidate from the links of the top post.

  • 2.5.x is still working on my side
  • 3.x is updated with the latest release candidate
1 Like

Thank you very much! 3.x is working fine for me, now…!

Did use the 3.2 bundle you recommend.
First check, my bmw items get populated with values again.
This seems to work.

THX !!

I’m running 3.1 within a Docker container and I’m unable to make the snapshot binding appear, here I what I did:

  • uninstalled BMW-connectedrive-binding (3.1.0) via the GUI
  • shutdown down OpenHAB: docker-compose stop inside the .yaml-folder
  • removed all traces of bmwconnected-drive*.jar from the docker-volumes in /var/lib/docker/volumes
  • Downloaded the 3.2-SNAPSHOT.jar (md5: 42f15e28e479f40205519a00bbcf51dd) and put it into the addons-volumnes (next to the README)
  • started OpenHAB via docker-compose start
  • When trying to install the binding via the GUI only shows me the 3.1.0 version of the binding

Which steps am I missing or am I doing wrong?

Turns out, it is loaded, but fails to load:

2021-10-05 10:19:05.093 [ERROR] [nternal.ConnectedDriveHandlerFactory] - bundle org.openhab.binding.bmwconnecteddrive:3.2.0.202110031048 (275)[org.openhab.binding.bmwconnecteddrive.internal.ConnectedDriveHandlerFactory(326)] : Error during instantiation of the implementation object
java.lang.IllegalArgumentException: argument type mismatch

The fixes are merged just 2 days ago and will be part of next the upcoming snapshot. I guess installation from GUI isn’t possible right now.
So keep your docker as it is, don’t install BMWConnectedDrive via GUI. I see for docker addon folder is mapped to /openhab/addons. Simply drop the bundle from top post into this folder and you should be fine.

Yeah, as I tried to point out by listing my steps, I thought I had to install it after putting it to the addons directory - but in fact it is loaded automatically when put there.

It doesn’t work though, this is the error I get:

2021-10-05 10:19:05.093 [ERROR] [nternal.ConnectedDriveHandlerFactory] - bundle org.openhab.binding.bmwconnecteddrive:3.2.0.202110031048 (275)[org.openhab.binding.bmwconnecteddrive.internal.ConnectedDriveHandlerFactory(326)] : Error during instantiation of the implementation object
java.lang.IllegalArgumentException: argument type mismatch

I can provide the whole backtrace if useful.

If the HandlerFactory cannot be instantiated, which is the first class without any binding specific implementation, it looks more like a fundamental problem. I would propose to check the stable OH 3.1 version first or at least the latest OH 3.2 Milestone.

Stable version of what? OpenHab? Or this binding? I’m lost, I don’t know where to get the 3.1-version of this binding which fixes the API-changed BMW did.

Hi! Since Yesterday it seems that not all channels are working. For the “Gesamtlaufzeit Statistik” and “Statistik der letzten Fahrt” I receive only NULL values, while the other channels are working fine. Is it only me or does someone else has the same issue?

I’ve just install the latest Milestone 3.2.0M4, the binding version seems to have an issue with my account at least. Log details below. I’ve tried to uninstall the Binding and drop the version at the top of the post into the addons folder, this doesn’t seem to have any affect. As if the binding doesn’t load.

It was all working fine with 3.1.0 and that above binding.

2021-11-11 17:31:35.718 [DEBUG] [.handler.ConnectedDriveBridgeHandler] - Prefer MyBMW API false
2021-11-11 17:31:35.855 [WARN ] [ternal.handler.VehicleChannelHandler] - ConnectedDrive Proxy isn't present
2021-11-11 17:31:35.962 [DEBUG] [.handler.ConnectedDriveBridgeHandler] - Update 1 things
2021-11-11 17:31:35.967 [DEBUG] [internal.handler.ConnectedDriveProxy] - updateLegacyToken
2021-11-11 17:31:36.833 [INFO ] [internal.handler.ConnectedDriveProxy] - Token valid? true
2021-11-11 17:31:37.102 [DEBUG] [internal.handler.ConnectedDriveProxy] - HTTP Error https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/VIN/status - 410 -
 Gonenull
2021-11-11 17:31:37.103 [DEBUG] [ternal.handler.VehicleChannelHandler] - https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/VIN/status - 410 - Gonenull
2021-11-11 17:31:37.103 [DEBUG] [ternal.handler.VehicleChannelHandler] - VehicleStatus not found - try legacy API
2021-11-11 17:31:37.236 [DEBUG] [internal.handler.ConnectedDriveProxy] - HTTP Error https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/VIN/statistics/las
tTrip - 410 - Gonenull
2021-11-11 17:31:37.237 [DEBUG] [ternal.handler.VehicleChannelHandler] - https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/VIN/statistics/lastTrip - 410
 - Gonenull
2021-11-11 17:31:37.332 [DEBUG] [internal.handler.ConnectedDriveProxy] - HTTP Error https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/VIN/statistics/all
Trips - 410 - Gonenull
2021-11-11 17:31:37.332 [DEBUG] [ternal.handler.VehicleChannelHandler] - https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/VIN/statistics/allTrips - 410
 - Gonenull
2021-11-11 17:31:37.430 [DEBUG] [internal.handler.ConnectedDriveProxy] - HTTP Error https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/VIN/destinations -
 410 - Gonenull
2021-11-11 17:31:37.431 [DEBUG] [ternal.handler.VehicleChannelHandler] - https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/VIN/destinations - 410 - Gone
null
2021-11-11 17:31:37.852 [DEBUG] [ternal.handler.VehicleChannelHandler] - ###### Vehicle Troubleshoot Fingerprint Data - BEGIN ######
2021-11-11 17:31:37.853 [DEBUG] [ternal.handler.VehicleChannelHandler] - ### Discovery Result ###
2021-11-11 17:31:37.854 [DEBUG] [ternal.handler.VehicleChannelHandler] - Invalid
2021-11-11 17:31:37.855 [DEBUG] [ternal.handler.VehicleChannelHandler] - ### Vehicle Status ###
2021-11-11 17:31:37.862 [DEBUG] [ternal.handler.VehicleChannelHandler] - null
2021-11-11 17:31:37.863 [DEBUG] [ternal.handler.VehicleChannelHandler] - ### Last Trip ###
2021-11-11 17:31:37.864 [DEBUG] [ternal.handler.VehicleChannelHandler] - {"url":"https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/Anonymous/statistics/lastTrip","sta
tus":410,"reason":"Gone","params":"null"}
2021-11-11 17:31:37.865 [DEBUG] [ternal.handler.VehicleChannelHandler] - ### All Trips ###
2021-11-11 17:31:37.866 [DEBUG] [ternal.handler.VehicleChannelHandler] - {"url":"https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/Anonymous/statistics/allTrips","sta
tus":410,"reason":"Gone","params":"null"}
2021-11-11 17:31:37.867 [DEBUG] [ternal.handler.VehicleChannelHandler] - ### Charge Profile ###
2021-11-11 17:31:37.883 [DEBUG] [ternal.handler.VehicleChannelHandler] - ### Range Map Empty ###
2021-11-11 17:31:37.884 [DEBUG] [ternal.handler.VehicleChannelHandler] - ###### Vehicle Troubleshoot Fingerprint Data - END ######
2021-11-11 17:31:38.352 [DEBUG] [.handler.ConnectedDriveBridgeHandler] - ###### Discovery Troubleshoot Fingerprint Data - BEGIN ######
2021-11-11 17:31:38.353 [DEBUG] [.handler.ConnectedDriveBridgeHandler] - ### Discovery Result ###
2021-11-11 17:31:38.355 [DEBUG] [.handler.ConnectedDriveBridgeHandler] - {"vehicles":[{"vin":"Anonymous","model":"Cooper","driveTrain":"CONV","brand":"MINI","yearOfCons
truction":2020,"bodytype":"F56","color":"STARLIGHT BLUE METALLIC","statisticsCommunityEnabled":false,"statisticsAvailable":false,"hasAlarmSystem":true,"dealer":{"name":
"Anonymous","street":"Anonymous","postalCode":"Anonymous","city":"Anonymous","country":"Anonymous","phone":"Anonymous"},"breakdownNumber":"Anonymous","chargingControl":
"NOT_SUPPORTED","vehicleFinder":"ACTIVATED","hornBlow":"NOT_SUPPORTED","lightFlash":"ACTIVATED","doorLock":"ACTIVATED","doorUnlock":"ACTIVATED","climateNow":"ACTIVATED"
,"sendPoi":"ACTIVATED","remote360":"NOT_SUPPORTED","climateControl":"START_TIMER","chargeNow":"NOT_SUPPORTED","lastDestinations":"NOT_SUPPORTED","carCloud":"ACTIVATED",
"remoteSoftwareUpgrade":"NOT_SUPPORTED","climateNowRES":"NOT_SUPPORTED","climateControlRES":"NOT_SUPPORTED","smartSolution":"NOT_SUPPORTED","ipa":"ACTIVATED"}]}
2021-11-11 17:31:38.355 [DEBUG] [.handler.ConnectedDriveBridgeHandler] - ###### Discovery Troubleshoot Fingerprint Data - END ######
2021-11-11 17:36:37.040 [DEBUG] [internal.handler.ConnectedDriveProxy] - HTTP Error https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/VIN/status - 410 -
 Gonenull
2021-11-11 17:36:37.041 [DEBUG] [ternal.handler.VehicleChannelHandler] - https://b2vapi.bmwgroup.com/webapi/v1/user/vehicles/VIN/status - 410 - Gonenull

Yes, I can confirm too. Stopped working on my side Nov. 9th at 10:15.
Don’t know if it’s a temporary problem or if BMW is updating their API again

1 Like

Please check the configuration of your vehicle thing. Seems the VIN is set to VIN and not the real identification number of your car.

It’s set correctly, I replaced the entry so as to not show my actual vin. Good to know it’s not just me that’s having the issue.

Same here.

All the statistics channels return NULL value, in both operation modes (“MyBMW API” vs “BMW Connected Drive”).

Openhab version: 3.1.0 (Build)
Binding version: org.openhab.binding.bmwconnecteddrive-3.2.0-20211112.032509-1.jar

Do you need further information?

Regards
Christian

openhab> things show bmwconnecteddrive:bev:yyy:XXX
UID: bmwconnecteddrive:bev:yyy:XXX
Type: bmwconnecteddrive:bev
Label: BMW i3 (CAR)
Status: ONLINE
Bridge: bmwconnecteddrive:account:yyy
Properties:
vehicleColor : CAPPARISWEISS MIT AKZENT BMW I BLAU
vehicleChargeControl : I3s 120
dealerAddress : Dealer
vehicleBodytype : I01
servicesActivated : VehicleFinder HornBlow LightFlash DoorLock DoorUnlock ClimateNow SendPoi CarCloud Ipa
vehicleChargeModes : AC_LOW DC
dealerPhone : 0049
servicesSupported : LastDestinations Statistics
supportBreakdownNumber : +4989358957103
vehicleBrand : BMW_I
servicesNotSupported : Remote360 ClimateControl ChargeNow RemoteSoftwareUpgrade ClimateNowRES ClimateControlRES SmartSolution
dealer : Dealer
vehicleModel : i3s 120
vehicleDriveTrain : BEV
vehicleAlarmSystem : Not Available
vehicleConstructionYear : 2021