PV surplous not available but it is

[traylenator]

I think I'm very close but something not correct.

When in "eco mode" the app always displays: Charging Paused , PV Surplus not available.

Working through the PVSURPLUS docs.

Automation is in place and running using the blueprint

alias: go-eCharger PV Surplus Charging
description: ""
use_blueprint:
  path: marq24/go-echarger-pv-surplus-data.yaml
  input:
    car_connected_entity:
      entity_id: binary_sensor.goe_XXXXX_car_0
    grid_single_entity: sensor.envoy_YYYYYYY_current_net_power_consumption
    battery_enabled: false
    pv_entities:
      - sensor.envoy_YYYYYYY_current_power_production

The current_net_power_consumption is indeed:

• Negative when it's sunny and there is spare capacity.
• Positive when it's nighttime.

The optional current_power_production is

• high when its sunny
• ~0 at night.

Other configs:

• Grid Target: -500W
• Logic Mode: Awatter [ECO]
• Age of inverter data is always less than 5 seconds as expected.
• Use PV surplous is ticked.
• Use Awatter is unticked ( though I have set it up for France, I don't have this available.)
• 'Allow Charge Pause (car compatibility) is ticked
• Automatic stop remain in Awatter is unticked.

In the go-E sensors:

• last pv superplus calculation is typically below 30seconds.
• age of inverter data is is less than 5 seconds.

I am not sure I have set:

• enable the 'Allow Charge Pause (car compatibility)' [API-Key 'acp']

Can you see the calculation that e-go charger made?

[traylenator]

The flattened automation:

variables:
  car_connected_entity:
    entity_id: binary_sensor.goe_XXXXXXX_car_0
  grid_single_entity: sensor.envoy_YYYYYYYYY_current_net_power_consumption
  grid_single_invert: false
  grid_consumption: null
  grid_feedin: null
  grid_phases: []
  grid_phases_invert: false
  pv_list:
    - sensor.envoy_YYYYYYYYYY_current_power_production
  pv_invert_flag: false
  battery_enable: false
  battery_list: []
  battery_invert_flag: false
  pgrid_value: |
    {% if grid_single_entity %}
      {% set value = states(grid_single_entity) | float(0) %}
      {{ (value * -1) if grid_single_invert else value }}
    {% elif grid_consumption and grid_feedin %}
      {% set cons_val = states(grid_consumption) | float(0) %}
      {% set feed_val = states(grid_feedin) | float(0) %}
      {{ cons_val - feed_val }}
    {% elif grid_phases | length >= 3 %}
      {% set ns = namespace(total=0) %}
      {% for entity in grid_phases[:3] %}
        {% set ns.total = ns.total + (states(entity) | float(0)) %}
      {% endfor %}
      {{ (ns.total * -1) if grid_phases_invert else ns.total }}
    {% else %}
      0
    {% endif %}
  ppv_value: |
    {% set ns = namespace(total=0) %} {% for entity in pv_list %}
      {% set ns.total = ns.total + (states(entity) | float(0)) %}
    {% endfor %} {{ (ns.total * -1) if pv_invert_flag else ns.total }}
  pakku_value: |
    {% if battery_enable %}
      {% set ns = namespace(total=0) %}
      {% for entity in battery_list %}
        {% set ns.total = ns.total + (states(entity) | float(0)) %}
      {% endfor %}
      {{ (ns.total * -1) if battery_invert_flag else ns.total }}
    {% else %}
      0
    {% endif %}
triggers:
  - trigger: time_pattern
    seconds: /5
conditions:
  - condition: and
    conditions:
      - condition: template
        value_template: '{{ states(car_connected_entity.entity_id)=="on" }}'
      - condition: sun
        after: sunrise
      - condition: sun
        before: sunset
actions:
  - action: goecharger_api2.set_pv_data
    data:
      pgrid: '{{ pgrid_value | round(0) | int }}'
      ppv: '{{ ppv_value | round(0) | int }}'
      pakku: '{{ pakku_value | round(0) | int }}'
mode: single
id: '1774796693847'
alias: go-eCharger PV Surplus Charging
description: ''

[marq24]

what's the value of frc ?!

[traylenator]

Frc:

{"frc":0}

i.e the Force State is Neutral.

[marq24]

and this 'https://github.com/marq24/ha-goecharger-api2/blob/main/docs/PVSURPLUS.md#finally-verify-if-the-wallbox-receives-your-data-from-the-automation' will also generate some output - so the device is really receiving data?

Concerning acp this is highly dependant from your car - also often there is a min required power before charging will/can start (also car dependent)

[traylenator]

So the numbers are getting though:

{"pgrid":-4,"ppv":5,"pakku":0}   

and

{"pvopt_averagePGrid":-4,"pvopt_averagePPv":5,"pvopt_averagePAkku":0}

• also often there is a min required power before charging will/can start

There's enough 🌞 now to fully load car ( Renault 5 ) and some to spare.

I do note that the car was in "Completed State" if I hit charge now on the car's app nothing happens as the charger is saying no I presume. I have checked I disabled all of the car's charging windows.

[traylenator]

Should have the starting power level is (fst)

{"fst":1400}

We have unit problem W vs kW ?

[marq24]

you need to send the data in Watts - not kW... so a value of -4 is way to low...

[traylenator]

Yeah that looking a lot better.
Thanks for the pointers.

[killamilla0815]

I have the same problem, it appears mostly when PV-surplus charging started and then after some time, it gets interrupted due to cloudy weather, which is expected. But then, when there surplus is back (>1,6kW) and ready to continue charging, I often notice that it doesnt.
When I connect diretly to the API via http:///api/status?filter=pakku,ppv,pgrid all 3 values are NULL, although 2 of them should reflect the current state ("ppv" and "pgrid", haven't configured the 3rd one "pakku").

For some reason the integation won't send any data.
What I've tried so far:

• dis-/enable the integration --> doesn't help
• restart the Automation yaml --> doesn' help
• restart all yaml's --> doesn't help
• reboot HA --> that solves it temporarly and values are back

This issue is highly reproducible on my side, not idea how to fix it, current go-E FW is 59.4, anyone have an idea ?

Thanks.

[marq24]

... with every automation run a trace will be created, the Integration is not responsible to start any automation, that is the task of your HA installation - so IF any automation does not start/run when expected - check your HA...

[marq24]

IF the automation is running (every 5sec) but there is no (new) data from the Integration sensors - that's a different story - but this would mean that the complete integration is stalled (all values) - THEN you might like to disable the WebSocket part...