Evcc API vehicle connected

[stadlaa]

Hello evcc community,

I am developing a system to charge with evcc + a PV-forecast. Therefore I need to know if a car is currently connected to the loadpoint via the API in order know if it is currently able to charge.

Sadly I couldn't find this parameter under /api/state. Is it possible to add it to the loadpoint or vehicle section and for any vehicle that has no online-interface just leave it on false?

Is there a good workaround available for my problem e.g. via the vehicle API (in my case Renault ZOE)? If so could someone give me instruction on how to do that?

[VolkerK62]

In /api/state in the loadpoints section there is connected and vehicleName.

[stadlaa]

I'm sorry if I missed something!

But here is my API request, the vehicle name is there, connection state (which schould be false) I cannot find, at least for ZOE:

Also, what does the "phaseAction" parameter mean?

Another strange thing is that the chargePower states 12098.06W but the vehicle isn't even physically connected!

"vehicles": {
     "ZOE": {
       "title": "ZOE",
       "icon": "car",
       "capacity": 43,
       "minSoc": 55,
       "limitSoc": 90
   }
}

"loadpoints": [
      {
        "chargeCurrent": 32,
        "chargePower": 12098.06,
        "chargerFeatureHeating": false,
        "chargerFeatureIntegratedDevice": false,
        "chargerIcon": null,
        "chargerPhases1p3p": true,
        "chargerPhysicalPhases": null,
        "disableThreshold": 0,
        "effectiveLimitSoc": 90,
        "effectiveMaxCurrent": 32,
        "effectiveMinCurrent": 10,
        "effectivePlanSoc": 0,
        "effectivePlanTime": "0001-01-01T00:00:00Z",
        "effectivePriority": 5,
        "enableThreshold": 0,
        "limitEnergy": 0,
        "limitSoc": 0,
        "maxCurrent": 32,
        "minCurrent": 10,
        "mode": "pv",
        "phaseAction": "inactive",
        "phaseRemaining": 0,
        "phasesActive": 3,
        "phasesConfigured": 3,
        "phasesEnabled": 3,
        "planEnergy": 0,
        "planTime": "0001-01-01T00:00:00Z",
        "priority": 5,
        "pvAction": "inactive",
        "pvRemaining": 0,
        "title": "Garage",
        "vehicleClimaterActive": null,
        "vehicleDetectionActive": false,
        "vehicleName": "ZOE",
        "vehicleOdometer": 0,
        "vehicleRange": 0,
        "vehicleSoc": 0,
        "vehicleTargetSoc": 0
      }

[VolkerK62]

Ok, I don´t know why, but I have got more information. Including charging and connected.

"loadpoints": [
            {
                "chargeCurrent": 0,
                "chargeCurrents": [
                    0,
                    0,
                    0
                ],
                "chargeDuration": 720000000000,
                "chargePower": 0,
                "chargeRemainingDuration": 0,
                "chargeRemainingEnergy": 15211.111111111066,
                "chargeTotalImport": 1769.2,
                "chargeVoltages": [
                    233.3,
                    0,
                    0
                ],
                "chargedEnergy": 200.00000000004547,
                "chargerFeatureHeating": false,
                "chargerFeatureIntegratedDevice": false,
                "chargerIcon": null,
                "chargerPhases1p3p": false,
                "chargerPhysicalPhases": null,
                "charging": false,
                "connected": true,
                "connectedDuration": 0,
                "disableThreshold": 0,

[stadlaa]

Okay I played around a bit and it turned out that my grid meter (that has currently no connection due to hardware changes) has been the issue (Api works fine now).

• If the grid-meter is not connected to the network evcc starts and throws the right error:
  Apr 25 09:06:10 raspberrypi evcc[61246]: [site ] ERROR 2024/04/25 09:06:10 grid meter: read failed: dial tcp 10.0.0.122:8899: i/o timeout
  But it has the strange behaviour I mentioned: vehicle is never connected, API is missing parameters: "charging" and "connecting"

• The strange displayed charge power was my fault, a family member started charging with the fronius wattpilot app without me noticing, due to the broken connected signal in evcc I did'nt realize that.

So why isn't it possible to use evcc without a working grid meter, as the vehicle API and the wallbox would be able to do their thing together? It seams that evcc stops operating after discovering the issue with the grid meter for the rest of the cycle. Therefore the charge-power is displayed right and the rest is just not touched.

Could this be changed to make charging possible without a working grid meter in the future to make evcc more robust?

Log with working grid-meter:

Apr 25 09:02:51 raspberrypi evcc[60147]: [site  ] DEBUG 2024/04/25 09:02:51 ----
Apr 25 09:02:51 raspberrypi evcc[60147]: [lp-1  ] DEBUG 2024/04/25 09:02:51 charge power: 0W
Apr 25 09:02:51 raspberrypi evcc[60147]: [site  ] DEBUG 2024/04/25 09:02:51 grid meter: 0W
Apr 25 09:02:51 raspberrypi evcc[60147]: [site  ] DEBUG 2024/04/25 09:02:51 pv power: 0W
Apr 25 09:02:51 raspberrypi evcc[60147]: [site  ] DEBUG 2024/04/25 09:02:51 site power: 0W
Apr 25 09:02:51 raspberrypi evcc[60147]: [lp-1  ] DEBUG 2024/04/25 09:02:51 charge currents: [0 0 0]A
Apr 25 09:02:51 raspberrypi evcc[60147]: [lp-1  ] DEBUG 2024/04/25 09:02:51 charger status: A
Apr 25 09:02:51 raspberrypi evcc[60147]: [lp-1  ] DEBUG 2024/04/25 09:02:51 next soc poll remaining time: 16m0s
Apr 25 09:03:01 raspberrypi evcc[60147]: [site  ] DEBUG 2024/04/25 09:03:01 ----

Log with disconnected grid-meter (stops after displaying charge power):

Apr 25 09:06:28 raspberrypi evcc[61246]: [site  ] DEBUG 2024/04/25 09:06:28 ----
Apr 25 09:06:28 raspberrypi evcc[61246]: [lp-1  ] DEBUG 2024/04/25 09:06:28 charge power: 0W
Apr 25 09:06:30 raspberrypi evcc[61246]: [site  ] ERROR 2024/04/25 09:06:30 grid meter: read failed: dial tcp 10.0.0.122:8899: i/o timeout
Apr 25 09:06:38 raspberrypi evcc[61246]: [site  ] DEBUG 2024/04/25 09:06:38 ----

btw my version is: 0.124.9

[VolkerK62]

don´t know if bug or feature.
you should open an issue for that.

[stadlaa]

Opened issue #13873