The equivalent for “estimatedPortableChargeDuration”. AC charging from the standard 230V power socket with a power adapter.
-
New plugin pimatic-bluelink
-
Thx for the new version I have installed it.
At the moment the charge time is showing this way, even the car is unplugged. This is okay for me.
But it does not change to AC when I plug the car. I tried it with the portable charger. I had a look to the JSON before charging and during. This is the relevant part of the json I think.
08:28:06.759 [pimatic-bluelink] debug:> "evStatus": { 08:28:06.759 [pimatic-bluelink] debug:> "batteryCharge": false, 08:28:06.759 [pimatic-bluelink] debug:> "batteryStatus": 75, 08:28:06.759 [pimatic-bluelink] debug:> "batteryPlugin": 2, 08:28:06.759 [pimatic-bluelink] debug:> "remainTime2": { 08:28:06.759 [pimatic-bluelink] debug:> "etc1": { 08:28:06.759 [pimatic-bluelink] debug:> "value": 125, 08:28:06.759 [pimatic-bluelink] debug:> "unit": 1 08:28:06.759 [pimatic-bluelink] debug:> }, 08:28:06.759 [pimatic-bluelink] debug:> "etc2": { 08:28:06.759 [pimatic-bluelink] debug:> "value": 600, 08:28:06.759 [pimatic-bluelink] debug:> "unit": 1 08:28:06.759 [pimatic-bluelink] debug:> }, 08:28:06.759 [pimatic-bluelink] debug:> "etc3": { 08:28:06.759 [pimatic-bluelink] debug:> "value": 200, 08:28:06.759 [pimatic-bluelink] debug:> "unit": 1 08:28:06.759 [pimatic-bluelink] debug:> }, 08:28:06.759 [pimatic-bluelink] debug:> "atc": { 08:28:06.759 [pimatic-bluelink] debug:> "value": 0, 08:28:06.759 [pimatic-bluelink] debug:> "unit": 1 08:28:06.759 [pimatic-bluelink] debug:> } 08:28:06.759 [pimatic-bluelink] debug:> },
Are you checking
batteryPlugin
to identify how the car is charging?
"batteryPlugin": 0,
should be unplugged
"batteryPlugin": 1,
should be DC
"batteryPlugin": 2,
should be AC portable
"batteryPlugin": 3,
should be AC standard (Wallbox)What is a bit crazy
"batteryCharge"
stays false, even the car was plugged. Maybe it takes more time to get the update. I plugged the car just a short time.I can verify this later today. I must drive to a fast charger, plug it to a wallbox…
EDIT
I now back at home and plugged the car to the AC portable plug. The UI shows changes now to AC. Seems I gave it not enough time…
But at the end it should be290 min (ACport)
I adapted the code a bit in my test system, because the better identifier for the charging type is
batteryPlugin
.# if evStatus.remainTime2.etc1.value > 0 if evStatus.batteryPlugin == 1 _chargingTime = evStatus.remainTime2.etc1.value + "min (DC)" # else if evStatus.remainTime2.etc3.value > 0 else if evStatus.batteryPlugin == 3 _chargingTime = evStatus.remainTime2.etc3.value + "min (AC)" # else if evStatus.remainTime2.etc2.value > 0 else if evStatus.batteryPlugin == 2 _chargingTime = evStatus.remainTime2.etc2.value + "min (ACport)" else _chargingTime = "no value" @setChargingTime(_chargingTime)
Now it shows:
I will drive to a FastCharger with DC and AC plugs later to verify if 1 really represents DC and 3 represents AC
-
It a bit tricky with AC and ACport. As I connected the car to AC the UI of Pimatic showed ACport. At home I plugged the car to the ACport and the UI shows again ACport.
batteryPlugin
was “2” in both cases… I will try it once more in the next days. DC works fine. -
At the moment I dont now to be honest. I need to drive once more to a fast charger. My wallbox is not installed yet. Will do this tomorrow.
-
I tried over the weekend to figure out how to identify AC and ACportable. I wasn’t able to find a way. Currently always ACport is shown independent of whether the car charges AC or AC portable. So I would suggest to use always AC and the related charging time for the UI.
ACport should only be required in emergency cases. Me for my own can life without it. What about the other users? -
No one seems to be against it…
@bertreb: If it would be okay for you, could you please adjust the plugin to evaluate AC instead of ACport when batteryPlugin=2? I think it is the more used and useful AC info.
-
Thank you!
-
Hey bertreb,
since two days I am getting no data from my car. I think something changed in the backend again.The log shows just this:
I haven’t changed anything in the config since weeks.
-
Yes, works again!
-
Hi,
once more Kia was changing the backend. No idea what they are doing. But it ends in error for the plugin.
I have updated bluelinky to the brand new version 7.3.0 and now it works again. Could you be so kind to update your plugin? -
Thanks for this!
-
Hey bertreb,
could you be so kind an update bluelinky to version 8.0.
I am facing problems to control my kia since some days. -
Thx, will give it a try!
Regarding v8, maybe I had a look on a different bluelinky repo…