OpenDTU Zero-Injection: Automatically limit inverters based on grid excess power with Home Assistant and OpenDTU up to a configurable Setpoint

README.md

OpenDTU Zero-Injection: Automatically limit inverters based on grid excess power with Home Assistant and OpenDTU up to a configurable Setpoint

Overview

This HA package allows you to automatically change your inverter production limit to match your home consumption in order to avoid an excessive grid excess.

It also integrates with 3ERL: depending on 3ERL API, the integration will either automaticlaly allow some production excess (when market electricity prices are positive, to make money) or will automaticlally regulate the production limit to avoid any excess when market electricity prices are negative.

Toolbar

The toolbar lets you view and control the main configuration and state:

• Inverters: the number of inverters you have

• Min: the minimum amount of power that your inverters will output. This should be set to a value matching your typical minimum power threshold used by your home. For example if your home uses always more than 800W and you have 8 inverters, then set it to 100W.

• Max: the nominal nominal power of the inverters (400W, 500W, 1000W, etc)

• Limit: the current production limit applied to inverters. This will be automatically set but can be also set manually.

• Setpoint: this is the desired level of excess to try to match. This value is automatically managed but can be manually overriden also.

• Production: the total production of your solar plant

Left Section - Monitoring

Global Home Power Flowing

This cool chart allows you to see how the power is flowing from the grid and from the solar panels to your house. I also added my OpenEVSE car charger,water heater and some other stuff but these are optional.

What is important:

• The grid voltage: useful to monitor during production spikes to troubleshoot high grid voltage causing inverters to stop
• The grid power (positive or negative)
• The produced solar power
• The maximum voltage of all inverters: inverters are increasing their voltage compared to the grid: the more the powr the more the voltage difference increases, which is more likely to reach the voltage limit when they stop producing and wait

Inverter Power

This section allows you to see each inverter AC power output.

The recycle icon allows you to retsart an inverter, which can be useful if it stopped producing for some reaosns and you want to reboot it before it recovers by itself.

Inverter Limit

This section displays the live inverter limit for each one and the recycle icon allows you to quickly reset an inverter's limit to 100%.

Right Section - Graphs

The graphs on the right allows to monitor the power, energy, temperature and limits.

Each graph is grayed out for the period when 3RL asked to limit our production. This is a way to easily see what happens to the power, energy, limit, etc depending if it was a period where we had to limit our production or we were allowing to inject in the grid network.

Installation

3ERL Intgeration

First install the 3ERL integration here to get the 3ERL Zero-Inject instructions and daily prices.

OpenDTU

Then configure your inverters in OpenDTU with an appropriate naming like Inverter S/N and activate HA integration.

You sensors in HA should be something like: sensor.inverter_1410a01e2cdd_*

WARNING

OpenDTU can only send one command at a time and reading inverter data or sending commands take about 1 second per inverter.

So this is a tradeoff between reading data fast and be up to date (OpenDTU polling can be 3 seconds), and have a slower correction time (1 minute), or at the opposite do not mind about readings (DTU polling 10 sec) and favor speed of updating limits (trigger could be 20 sec).

For monitoring purposes and to detect issues I prefer having a fast refresh, so I set my DTU polling to 3 seconds and my update limite rate 1 per minute.

Open OpenDTU console and look for log lines like this:

[14:42:58.575] I (1013189) hoymiles: Queue size - NRF: 0 CMT: 8

These indicate the number of messages sitting in the queue waiting to be processed and you will see the communiction errors. This number should at one point in time go down to 0 or at least be able to go down. You can look also at the last time data was updated in OpeNDTU interface for all inverters. The more you have a big last update time, the more teh DTU is unable to read your inverters.

solar.yaml

Make sure you have configured Home Assistant to support packages.

homeassistant:
  packages: !include_dir_named packages

Put the file solar.yaml in the packages folder:

Edit solar.yaml according to your needs.

I have left some TODO comments in the file to indicate what to do.

view.yaml

• Edit your current dashboard
• Add a new view
• Click on the 3 points on the right to display the yaml of the view
• Paste the content of view.yaml

To work properly, you will need to install these frontend plugins from HACS:

• Power Flow Card Plus
• Lovelace Entity Progress Card
• Plotly Graph Card
• Bar Card
• Entity Progress Card

solar.yaml

##########
# Automatically limit inverters based on grid excess with Home Assistant and OpenDTU
# Ref: https://gist.github.com/mathieucarbou/382556f1279d612962e03232544692d1
#
# SPDX-License-Identifier: MIT
# Copyright (C) Mathieu Carbou
##########

# https://www.home-assistant.io/integrations/input_number
input_number:
  # 🖐️ Number of inverters
  inverters_count:
    name: Inverters Count
    min: 0
    max: 20
    step: 1
    mode: box
  # 🖐️ Inverters nominal power, usually 400W, 500W, 1000W, etc
  inverters_nominal_power:
    name: Inverters Nominal Power
    unit_of_measurement: W
    min: 0
    max: 2000
    step: 1
    mode: box
  # 🖐️ Inverters minimal power, usually 50W, 100W. Has to be more than 10W to keep the iverters workimng
  # This should be such that minimalPowerLimit * number of inverters == minimal home consumption
  # Default: 50W
  inverters_minimal_power:
    name: Inverters Minimal Power
    unit_of_measurement: W
    min: 10
    max: 2000
    step: 1
    mode: box
  # Limit sent to inverters. Will be automatically computed but can be manually set also.
  inverters_power_limit:
    name: Inverters Power Limit
    unit_of_measurement: W
    min: 0
    max: 2000
    step: 1
    mode: box
  # Target excess or import to stay close to
  # Will be automatically set based on below automations but can also beset manually
  # Default is 0
  inverters_excess_setpoint:
    name: Inverters Excess Setpoint
    unit_of_measurement: W
    min: -10000
    max: 10000
    step: 1
    mode: box

template:
  # https://www.home-assistant.io/integrations/template/#sensor
  - sensor:
      # Get the maximum voltage of inverters to detect potential risk of production stop
      # 🖐️ Put your inverter S/N in this list in lowercase, any order
      - name: Max Inverter Voltage
        unique_id: 42D1A95B-7A70-46CF-9734-497CDDCE5674
        state_class: measurement
        device_class: voltage
        unit_of_measurement: V
        state: >-
          {{ ['1410a01ec916', '1410a01ed6ca', '1410a01ed5a9', '1410a01ed5f0', '1410a01f092d', '1410a01ed604', '1410a01f010c', '1410a01e2cdd']|map('regex_replace', '(.+)', "sensor.inverter_\\1_voltage")|map('states')|map('float', 0)|max }}

      # Get the maximum temeprature of inverters to detect potential risk of production stop
      # 🖐️ Put your inverter S/N in this list in lowercase, any order
      - name: Max Inverter Temperature
        unique_id: 272E179C-3A11-44A1-B674-8C5A603033A0
        state_class: measurement
        device_class: temperature
        unit_of_measurement: "°C"
        state: >-
          {{ ['1410a01ec916', '1410a01ed6ca', '1410a01ed5a9', '1410a01ed5f0', '1410a01f092d', '1410a01ed604', '1410a01f010c', '1410a01e2cdd']|map('regex_replace', '(.+)', "sensor.inverter_\\1_temperature")|map('states')|map('float', 0)|max }}

      # This sensor computes your inverters energy and makes sure it does not reset to 0
      # 🖐️ Put your OpenDTU YieldTotal sensor or Shelly sensors
      - name: Inverters Energy
        unique_id: "011F19F7-E337-488E-B52E-3CC75CBD816A"
        state_class: total_increasing
        device_class: energy
        unit_of_measurement: kWh
        # CHOICE #1: Use Shelly (could miss data if Shelly's are down - but more reliable)
        state: >-
          {% set c = states('sensor.inverters_energy')|float(0) %}
          {% set gA = states('sensor.solar_plant_group_a_total_active_energy')|float(0) %}
          {% set gB = states('sensor.solar_plant_group_b_total_active_energy')|float(0) %}
          {{ [c, gA + gB] | max }}
        # CHOICE #2: Use energy counters stored in inverters from OpenDTU (could miss data if inverters are unreachable - which can sometimes happen while the yare producing)
        # state: >-
        #   {% set c = states('sensor.inverters_energy')|float(0) %}
        #   {% set e = states('sensor.opendtu_ff4930_yield_total')|float(0) %}
        #   {{ [c, e] | max }}

      # Total Solar Production Power
      # 🖐️ Make sure you have a sensor called Solar Production Power which reflects your total plant production power.
      # In my case, I have 2 production groups, so I create a sensor which summarizes both here.
      - name: Solar Production Power
        unique_id: "01e37eed-3045-4eee-a786-1249567fe300"
        state_class: measurement
        device_class: power
        unit_of_measurement: W
        availability: "{{ has_value('sensor.solar_plant_group_a_power') and has_value('sensor.solar_plant_group_b_power') }}"
        state: "{{ states('sensor.solar_plant_group_a_power')|float + states('sensor.solar_plant_group_b_power')|float }}"

      # Home Consumed Power: power consumed by your house == the produced power plus the measured grid power
      # 🖐️ Configure your sensor measuring your grid power here. Mine is a Shelly and is called: sensor.grid_power
      - name: Home Consumed Power
        unique_id: BE34D1AD-AB8E-4909-ACE0-BBA7D3877105
        state_class: measurement
        device_class: power
        unit_of_measurement: W
        availability: "{{ has_value('sensor.solar_production_power') and has_value('sensor.grid_power') }}"
        state: "{{ states('sensor.solar_production_power')|float + states('sensor.grid_power')|float }}"

      # Solar Consumed Power: This is the produced power consumed by your house
      - name: Solar Consumed Power
        unique_id: "01e37eed-3045-4eee-a786-1249567fe303"
        state_class: measurement
        device_class: power
        unit_of_measurement: W
        availability: "{{ has_value('sensor.solar_production_power') and has_value('sensor.grid_power') }}"
        state: "{{ [states('sensor.solar_production_power')|float + [states('sensor.grid_power')|float, 0] | min, 0] | max }}"

      # Daily energy used from solar production (C = P - E)
      - name: Solar Consumed Energy Meter Daily
        unique_id: "01e37eed-3045-4eee-a786-1249567fe305"
        state_class: total_increasing
        device_class: energy
        unit_of_measurement: kWh
        availability: "{{ has_value('sensor.inverters_energy_meter_daily') and has_value('sensor.grid_energy_returned_meter_daily') }}"
        state: >-
          {% set p = states('sensor.inverters_energy_meter_daily')|float(0) %}
          {% set e = states('sensor.grid_energy_returned_meter_daily')|float(0) %}
          {% set c = states('sensor.solar_consumed_energy_meter_daily')|float(0) %}
          {{ [0 if p == 0 or p < c or p < e else c, [0, p - e] | max] | max }}

      # Daily energy consumed by home (H = P + I - E)
      - name: Home Consumed Energy Meter Daily
        unique_id: A03E558E-DF44-4DAB-852D-0847287DEDDB
        state_class: total_increasing
        device_class: energy
        unit_of_measurement: kWh
        availability: "{{ has_value('sensor.inverters_energy_meter_daily') and has_value('sensor.grid_energy_meter_daily') and has_value('sensor.grid_energy_returned_meter_daily') }}"
        state: >-
          {% set p = states('sensor.inverters_energy_meter_daily')|float(0) %}
          {% set i = states('sensor.grid_energy_meter_daily')|float(0) %}
          {% set e = states('sensor.grid_energy_returned_meter_daily')|float(0) %}
          {% set h = states('sensor.home_consumed_energy_meter_daily')|float(0) %}
          {{ [0, p + i - e] | max if p == 0 or i == 0 or p < e else [h, p + i - e] | max }}

# https://www.home-assistant.io/integrations/utility_meter/
utility_meter:
  # Grid Energy Returned Meter Daily: Daily meter for the grid returned energy.
  # Mine comes from a Linky key which is far more reliable than a Shelly since reads the counters directly stored in the Linky
  # 🖐️ Set your grid returned energy sensor here
  grid_energy_returned_meter_daily:
    name: Grid Energy Returned Meter Daily
    unique_id: 454B7731-375D-4C90-AFC0-42EAB23DF11D
    source: sensor.linky_energie_injectee
    cycle: daily
  # Inverters Energy Meter Daily
  inverters_energy_meter_daily:
    name: Inverters Energy Meter Daily
    unique_id: 4C4D8D06-C9D2-4408-B21A-1274A6E0F041
    source: sensor.inverters_energy
    cycle: daily

# https://www.home-assistant.io/docs/automation/
automation:
  # Automatically propagate changes in power limit input number to inverters
  - id: "0000000000038"
    alias: "Solar: Update Inverter Power Limit"
    trigger:
      - trigger: state
        entity_id:
          - input_number.inverters_power_limit
    condition: []
    action:
      - action: number.set_value
        data:
          value: >-
            {% set minimalPowerLimit = states('input_number.inverters_minimal_power')|int(50) %}
            {% set nominalPower = states('input_number.inverters_nominal_power')|int(minimalPowerLimit) %}
            {% set powerLimit = states('input_number.inverters_power_limit')|float(nominalPower) %}
            {{ powerLimit / nominalPower * 100.0 }}
        target:
          entity_id:
            - number.inverter_1410a01e2cdd_limit_nonpersistent_relative
            - number.inverter_1410a01ec916_limit_nonpersistent_relative
            - number.inverter_1410a01ed6ca_limit_nonpersistent_relative
            - number.inverter_1410a01ed5a9_limit_nonpersistent_relative
            - number.inverter_1410a01ed5f0_limit_nonpersistent_relative
            - number.inverter_1410a01f092d_limit_nonpersistent_relative
            - number.inverter_1410a01ed604_limit_nonpersistent_relative
            - number.inverter_1410a01f010c_limit_nonpersistent_relative

  # Runs at a frequent interval to update the inverters limit
  # 🖐️ set your Grid Power sensor for `sensor.grid_power`
  # 🖐️ Update the list of entity IDs matching your inverters S/N: these sensors come from OpenDTU
  - id: "0000000000039"
    alias: "Solar: Auto update power limits"
    trigger:
      - trigger: time_pattern
        #minutes: /1
        seconds: /30
    condition:
      - condition: state
        entity_id: binary_sensor.opendtu_ff4930_status
        state: "on"
    action:
      - action: input_number.set_value
        data:
          value: >-
            {% set minimalPowerLimit = states('input_number.inverters_minimal_power')|int(50) %}
            {% set grid = states('sensor.grid_power')|float(0) %}
            {% set setpoint = states('input_number.inverters_excess_setpoint')|int(0) %}
            {% set nominalPower = states('input_number.inverters_nominal_power')|int(minimalPowerLimit) %}
            {% set powerLimit = states('input_number.inverters_power_limit')|float(nominalPower) %}
            {% set count = states('input_number.inverters_count')|int(0) %}
            {% set missedPower = (grid - setpoint) / count if count > 0 else nominalPower %}
            {{ [nominalPower, [minimalPowerLimit, powerLimit + missedPower|round(0, "ceil")]|max]|min|round }}
        target:
          entity_id:
            - input_number.inverters_power_limit

  # Update the setpoint depending on events
  # 🖐️ set your events accordingly. For example, `binary_sensor.openevse_vehicle_connected` and `sensor.openevse_vehicle_battery_level` and `binary_sensor.openevse_vehicle_charge` are for my EV car charger. You might not need them.
  # 🖐️ update the conditions: here, I need a special condition that sets the setpoint to -600 when my EV si connected so that it has enough excess to start charging. If you do not have an EV, then put -200 or -100 or 0.
  # The value of -5500 is because with single phase in France you cannot divert to the grid more than 6kVA. So this is a safety value in case your home is consuming less, the script will reduce the soalr production ot make sure it does not feed teh grid with more than 5.5kW.
  - id: "0000000000041"
    alias: "Solar: Auto update Setpoint"
    triggers:
      - trigger: state
        entity_id:
          - binary_sensor.inverters_zero_inject
          - binary_sensor.openevse_vehicle_connected
          - sensor.openevse_vehicle_battery_level
          - binary_sensor.openevse_vehicle_charge
      - trigger: homeassistant
        event: start
    conditions: []
    actions:
      - if:
          - condition: state
            entity_id: binary_sensor.inverters_zero_inject
            state: "on"
        then:
          - if:
              - condition: state
                entity_id: binary_sensor.openevse_vehicle_connected
                state: "on"
              - condition: numeric_state
                entity_id: sensor.openevse_vehicle_battery_level
                below: 100
            then:
              - action: input_number.set_value
                metadata: {}
                data:
                  value: -600
                target:
                  entity_id: input_number.inverters_excess_setpoint
            else:
              - action: input_number.set_value
                metadata: {}
                data:
                  value: -200
                target:
                  entity_id: input_number.inverters_excess_setpoint
      - if:
          - condition: state
            entity_id: binary_sensor.inverters_zero_inject
            state: "off"
        then:
          - action: input_number.set_value
            metadata: {}
            data:
              value: -5500
            target:
              entity_id: input_number.inverters_excess_setpoint

  # Notification in case a high grid volatge is detected
  # This is optional and require you to know how to setup HA notifications.
  - id: "0000000000042"
    alias: "Solar: Notify of high grid voltage"
    trigger:
      - trigger: numeric_state
        entity_id:
          - sensor.grid_voltage
        above: 250
    action:
      - action: notify.whatsapp_mathieu
        data:
          message: "[GRID] High Voltage (> 250V)"
      - delay:
          hours: 0
          minutes: 1
          seconds: 0
          milliseconds: 0

view.yaml

type: sections
max_columns: 3
title: Solaire
path: solar
icon: mdi:solar-panel-large
sections:
  - type: grid
    cards:
      - type: custom:power-flow-card-plus
        entities:
          grid:
            entity: sensor.grid_power
            display_state: one_way
            secondary_info:
              entity: sensor.grid_voltage
              unit_of_measurement: V
              display_zero: true
              color_value: false
              decimals: 1
            use_metadata: false
            color_value: false
            color_icon: true
          solar:
            entity: sensor.solar_production_power
            display_zero_state: true
            color_value: false
            color_icon: true
            secondary_info:
              entity: sensor.max_inverter_voltage
              unit_of_measurement: V
              display_zero: true
              color_value: false
              decimals: 1
          home:
            entity: sensor.home_consumed_power
            color_value: false
            color_icon: true
            secondary_info: {}
          individual:
            - entity: sensor.openevse_power
              display_zero: true
              icon: mdi:car-electric
              name: OpenEVSE
              color_value: false
              color_icon: true
              secondary_info:
                entity: sensor.renault_zoe_battery_level
                unit_of_measurement: "%"
                display_zero: true
                unit_white_space: true
              display_zero_state: true
              unit_white_space: true
            - entity: sensor.chauffe_eau_power
              display_zero: true
              color_value: false
              color_icon: true
              secondary_info: {}
              name: Chauffe-eau
              icon: mdi:water-boiler
              calculate_flow_rate: false
              display_zero_state: true
              unit_white_space: true
            - entity: sensor.total_deshumidificateur_power
              display_zero: true
              color_value: false
              color_icon: true
              secondary_info: {}
              name: Déshumidificateurs
              icon: mdi:air-filter
              display_zero_state: true
              calculate_flow_rate: false
              unit_white_space: true
            - entity: sensor.total_pac_power
              display_zero: true
              color_value: false
              color_icon: true
              secondary_info: {}
              name: PAC
              icon: mdi:air-conditioner
              display_zero_state: true
              unit_white_space: true
        clickable_entities: true
        display_zero_lines:
          mode: show
          transparency: 50
          grey_color:
            - 189
            - 189
            - 189

Quel est ton avis sur ce point ?

L'intégration utilise le paramètre non persistent. Voir le code.

par contre certaines version du firmware hoymiles ont un bug et mettent les limites persistantes. Il faut voir avec le support pour une MAJ.

Hello.
Can you still get the PREP from RTE API (https://www.services-rte.com/cms/open_data/v1/price/table)?
It looks down since the end of 2025.

@RemixQ no I cannot. There has been a warning recently about the removal of v1 api. I need to check what to do.

@RemixQ that was a simple fix. I am actually using the same API they use in their web page here: https://www.services-rte.com/fr/visualisez-les-donnees-publiees-par-rte/equilibrage.html

Yes I see it, thanks. And let's see about the API deprecation, which is seems to be v2 in few months.

Yes I see it, thanks. And let's see about the API deprecation, which is seems to be v2 in few months.

Yes... I don't know yet how it will work.
For now I am looking at the XHR requests done by their web page to display the PER price graph.
I will wait to see how they change their web page first: if we are lucky, v2 will still be as "open" as now 😄

@RemixQ : updated again... They changed the api again