thanks Martin.
The remote command “climate-now-start” is working for me, but “stop-charging” not. It shows me: stop-charging error 403
It seems that my PHEV doesn’t support the stop-charging command.
…and one more question, Martin.
I tried to create a fingerprint - but wasn’t successfull. I am running openHAB 4.2.1 in a Synology Container and received the following error:
openhab> mybmw fingerprint
# Start fingerprint
### Account 1
###### Vehicles base for brand bmw
Fingerprint failed, network exception: { "statusCode": 403, "message": "Out of call volume quota. Quota will be replenished in 00:21:29." }
### End account 1
Exception zipping fingerprint: /openhab/mybmw/20240820
### Fingerprint has been written to files in directory: /openhab/mybmw/20240820
# End fingerprint
The directory /openhab/mybmw is already outside of the container and their is a lot of space.
The created zip-file is empty.
Not sure where the quota exception came from. Is there a workaround running this command in a docker container?
Yes, we already found out that PHEVs do not support start/stop charging.
You cannot create the fingerprint because you reached the limit of requests on the BMW server. Just wait for the next full hour and try again.
that explains everything - now it makes sense to me. Quota was not disk-related, but number of request related.
Thanks Tim for that info!
Originally I was searching for a possibility to stop charging at e.g. 80% but with that info and after reviewing the fingerprint I don’t see a possibility to stop the charging at a certain point.
I keep on having issues - it’s on and off. I’m running on 4.2.1 and on the binding version 4.1.3.202406222038.
I deleted both cars, added them back up, but the last one which I add is going offline over and over with these error messages:
The account itself is OK, but the car stays offline. It also drives OH into a high-CPU usage mode, up to 75% on a RPI4.
I’d be grateful for a fix or fixing idea Thanks!
Hi @Jagohu
If you run now on OH 4.2, why are you still using the 4.1.3 version of the addon? There is no need for that, you should be able to use the official 4.2 version.
Do you see the quota error in the log? It could be that you have to decrease the frequency of updates to keep the vehicles online. BMW introduced a quota on requests (see above), which causes some issues. Anyhow some time later it should recover automatically.
I’ve the same issue just my Error code is 403.
2024-09-18 06:59:42.761 [WARN ] [al.handler.auth.MyBMWTokenController] - Authorization Exception: URL: https://customer.bmwgroup.com/gcdm/oauth/authenticate, Error: 403, Message: 403403 Forbidden
My app showed me an update notice a couple of days ago. Car is an BMW i5.
The BMW account thing is still online. Just the car thing doesn’t work anymore.
@MathiasK , hmm maybe it could help if you delete the vehicle thing and start discovery again. 403 usually means you are not authorized. Did you enable all remote services in the car?
A PHEV or hybrid can not do stop/start charging
A BEV or full electric can do this without an issue
I can stop my i4 with openhab and restart it. The issue I currently have is that I can not control the charging speed so I use the app to set the charge speed at 6A-8A or a bit higher
depending how sunny the day is. Ideally I could adjust the charging speed depending on the solar panels
I’ve been stuck on “Vehicle State Update Failed” for about a month now. Usually deleting the thing and a re-scan solved the issue. Anyone else having this issue on 4.3.0.M2?