New plugin pimatic-bluelink

---

Ok, one conclusion is then that I change the 12V battery value back to api value batSoc 100->100%

Is this nice colored table created by yourself and where did you get the info from?

No it’s from awaccu (Dutch)

@incmve: As I can see you got EVNotify running. Which OBD dongle are you using? My seems to be incompatible with EVNotify (others OBD tools works).
@bertreb: This change comes up a while after your update to 0.2.26. I got a message over night from pimatic, that my 12V battery state drops (triggered by a rule). I think as well the API changed over night…

Regarding estimatedCurrentChargeDuration and tirePressureWarningLamp. I would give it a try. As you remember the tire pressure was indicated by the Car, but not in the JSON. Maybe this is different now due to source change you implement!? Lets try. I am pretty sure that estimatedCurrentChargeDuration has two possible states, one for AC and one for DC charging. Same as max range. It depends from the config of the charging limit of AC and DC

I changed the 12V battery status going from version 0.2.23 to 0.2.24. That you noticed changes in 0.2.26 came from the updated refresh in 0.2.26.
I changed 12V status back in 0.2.28 and added as a first charging value: estimatedCurrentChargeDuration.

The other available options are: estimatedFastChargeDuration, estimatedPortableChargeDuration and estimatedStationChargeDuration
Let me know which ones you want. And on the difference AC / DC give me the logic that make sense.

@ortin I got a simple ELM327

Thanks will order is. Like to use ABRP

@bertreb Is measured my 12V batter with a meter and it’s 12.22V, so that should be around 65%.
The plugin shows 69% so that seems to work :

@bertreb Could it be that de “Main Battery %” value is pulled from cache and the “Main Battery KM” value is realtime data?

When i do a refresh in Pimatic the “Main Battery KM” updates but the “Main Battery %” stays the same. 10sec later i do a refresh in the Bluelink app and both Values are updated (Bluelink app), when i refresh in Pimatic after a Bluelink update both valeus are updated and Pimatic and Bluelink app have the same data.

ps. Thanks for the good work

When you push refresh in the gui (or via rules) the data (incl Ev BatteryStatus) should come from the car.
The polled status updates (1 per hour) uses the cache. Using for a refresh the realtime data from the car was added in version 0.2.26.

I’ve been thinking a bit about how to elegantly integrate the charging time into the UI. I thought of the following, but I’m not sure if you can build it that way easily.

My idea is to change the text in the brackets according to the used power source.

Regarding the maxRange. It would be cool to see the charge limit level in brackets behind the value. It can be configured onboard the car or via UVO app.
Means something like this:

It would fill up the UI a bit, but it would be just consequent to add as well the maxRange for AC in the same way. If users don’t want to see, they can hide it via xAttributeOptions in the device config.

These are my ideas about it.

I understand the 3 charging time options. When you charge the type and the charging time available.
Are the maximum values, fixed values per charge type. So when you charge depending of the type you get the DC, AC or ACport maximum value?

For the maximum value there are two types available only as I know DC and AC.

  {
    "targetSOClevel": 100,
    "dte": {
      "rangeByFuel": {
        "evModeRange": {
          "value": 335,
          "unit": 1
        },
        "totalAvailableRange": {
          "value": 335,
          "unit": 1
        }
      },
      "type": 2
    },
    "plugType": 0
  },
  {
    "targetSOClevel": 80,
    "dte": {
      "rangeByFuel": {
        "evModeRange": {
          "value": 262,
          "unit": 1
        },
        "totalAvailableRange": {
          "value": 262,
          "unit": 1
        }
      },
      "type": 2
    },
    "plugType": 1
  }

"plugType": 0 means DC
"plugType": 1 means AC

The JSON show that DC has no limitation "targetSOClevel": 100, (max. 335km) and AC is limited to 80% "targetSOClevel": 80, (max. 262km)

Ok, and what is charging type ACport?

The equivalent for “estimatedPortableChargeDuration”. AC charging from the standard 230V power socket with a power adapter.

I added the AC/DC values in version 0.2.29

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 be 290 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

I’m made the changes in version 0.2.30.

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.

Hi, when batteryPlugin is 2 then it should be ACport. Or do is miss your point?

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.