-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Info about battery charging status and amount of kwh charged in last session #263
Comments
You can’t. That info is not available. Op 9 aug. 2023 om 12:17 heeft Simone Double B ***@***.***> het volgende geschreven:
Hi,
I'd like to ask if it's possible to retrieve the last amount of kWh charged in the battery for a Hyundai Kona Electric.
I saw in the vehicle.fullStatus() that there is evStatus property but it doesn't look to provide any info regarding the kWh charged by the car.
Does anybody know how to retrieve that info?
Thanks in advance
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Hi Pierre, Thanks for your reply. Also it's possible to see in the car the speed in kWh of current charge, would that be possible to be retrieve? Anyway I managed to discovered that by calling following status while having the car charging I received back
Response:
Is there a way to collect the actual response from BlueLink API about the car current status? I wonder if there might be some properties not parsed which could be also helpful. Thanks |
Luckily it correspondents, since it uses the exact same api calls to the hyundai/kia servers :)
Multiplying time by current and you have your answer (and you can calculate the losses in conversion)
… Op 10 aug. 2023, om 10:59 heeft Simone Double B ***@***.***> het volgende geschreven:
Hi Pierre,
Thanks for your reply.
That's a pity! It would have been useful to get the kWh charged to be able to calculate the cost of the charge.
Anyway I managed to discovered that by calling following status while having the car charging I received back engine.estimatedCurrentChargeDuration which actually correspond to the same estimation I have in the BlueLink app.
await vehicle.status({ refresh: false, parsed: true, useInfo: true});
Response:
{
"chassis": {
"hoodOpen": false,
"trunkOpen": false,
"locked": true,
"openDoors": {
"frontRight": false,
"frontLeft": false,
"backLeft": false,
"backRight": false
},
"tirePressureWarningLamp": {
"rearLeft": false,
"frontLeft": false,
"frontRight": false,
"rearRight": false,
"all": false
}
},
"climate": {
"active": false,
"steeringwheelHeat": false,
"sideMirrorHeat": false,
"rearWindowHeat": false,
"defrost": false,
"temperatureSetpoint": 15,
"temperatureUnit": 0
},
"engine": {
"ignition": false,
"accessory": false,
"range": 463,
"rangeEV": 463,
"plugedTo": 2,
"charging": true,
"estimatedCurrentChargeDuration": 95,
"estimatedFastChargeDuration": 1,
"estimatedPortableChargeDuration": 380,
"estimatedStationChargeDuration": 110,
"batteryCharge12v": 89,
"batteryChargeHV": 83
},
"lastupdate": "2023-08-09T11:50:22.000Z"
}
Is there a way to collect the actual response from BlueLink API about the car current status? I wonder if there might be some properties not parsed which could be also helpful.
Thanks
—
Reply to this email directly, view it on GitHub <#263 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO7MCGYO5PUYIYATGUFCVITXUSPGRANCNFSM6AAAAAA3JYSIBY>.
You are receiving this because you commented.
|
@PierreLevres Do you refer to assume the kWh speed of charging (taken live from the car manually), multiplied by |
Hi,
I'd like to ask if it's possible to retrieve the last amount of kWh charged in the battery for a Hyundai Kona Electric.
I saw in the vehicle.fullStatus() that there is evStatus property but it doesn't look to provide any info regarding the kWh charged by the car.
Also it would be nice to know how long it will take to charge the car to target.
Does anybody know how to retrieve that info?
Thanks in advance
The text was updated successfully, but these errors were encountered: