Solaredge Modbus Configuration for Single Inverter and Battery

DragonQ · March 17, 2023, 3:14pm

Any time I make sensors like this (that just round other sensors), the history graphs for those sensors always have weird spikes/troughs that do not appear in the original sensors.

ryanm101 · March 17, 2023, 3:22pm

Annoying but you could use the orig sensor for stats and the new rounding sensor for display… I hate the duplication of data but you could restrict the exporting of stats (if you do it) using the recorder to only the original sensors.

DragonQ · March 17, 2023, 3:28pm

I’ve only had my system installed for 2 days but I notice the import/export from grid value is almost never 0. Yesterday we exported 1 kWh of the 13 kWh we generated, even though the battery was never full. It was all in trickles throughout the day. Same with import, which was 0.5 kWh during the peak period, even though the battery was never empty either.

Is this normal? I wasn’t expecting “self consumption” to be 100% but I also didn’t expect it to be as low as 90%.

ryanm101 · March 17, 2023, 3:53pm

Guys,

I’ve two issues i’d like to solve so i’m firing this out here on the off chance someone can help / has already done it…

Problem 1:
Displaying Import / Export / Consumption my default ‘Energy Dashboard’ looks like:

Which annoys me as it shows the battery charging 0100-0800 as separate to import so taking 0100 as the example: Battery charged 3.57kWh and I imported 0.7kWh… Except NO i didnt I imported 4.2kWh and happened to use 3.6 to charge the battery… This imo should display the pink as a stack graph on top of import (blue), as import was used to charge NOT the sun.

Problem 2:
My solar system install was ~£14K
I’m using the battery to keep me on offpeak prices and exporting etc where i can.
I’d like four things:

Somewhere to enter my monthly bill
the ability to work out (I’ve done some of this in my repo)
a) what i would have paid based on my current tariffs,
b) what i did pay
c) what i saved (x saved by battery keeping me offpeak, y saved by solar covering my usage, z how much was saved charging battery from solar)
a counter that takes my £14K starting point and starts subtracting my savings and produces a current balance and how long based on avg to date it will take to ‘pay off’

ryanm101 · March 20, 2023, 5:03pm

solar_battery_from_panels_daily isnt showing up for me anywhere even though it is declared… anyone else seeing this? Nothing in logs either.

github.com

ryanm101/hasolarcfg/blob/dc9e4b8d301b43e427fb5635bff276fadd3139c2/packages/energy_utilities.yaml#L37

    
      
                - offpeak
            
          # Electricity Battery
            solar_battery_from_grid_daily:
              source: sensor.solar_grid_to_battery_kwh
              name: Solar Battery Imported Daily
              cycle: daily
              tariffs:
                - peak
                - offpeak
            solar_battery_from_panels_daily:
              source: sensor.solar_panel_to_battery_kwh
              name: Solar Battery Generated Daily
              cycle: daily
            solar_battery_in_daily:
              source: sensor.solar_battery_in_kwh
              name: Solar Battery In Daily
              cycle: daily
            solar_battery_out_daily:
              source: sensor.solar_battery_out_kwh
              name: Solar Battery Out Daily

Edit:

Ok found it… its Solar_Battery_Generated_Daily… its using the friendly name instead of the name of the sensor as declared… Stupid…

cannos88 · March 22, 2023, 4:26pm

hi all, I have a SE6000H inverter with meter. I configured the SolarEdge Modbus Multi Device custom repository. I currently have no battery. The meter is recognized well but I have no read value. On the inverter, however, I can read all the values. What could have happened?

WillCodeForCats · March 22, 2023, 6:38pm

The default precision setting in HA unfortunately only affects how the HA frontend displays it on cards and stuff, the entity itself doesn’t change precision when used in templates. In templates you have to add

| round(1)

to things if you want 1 decimal place, for example. Change 1 to however many decimals you want.

WillCodeForCats · March 22, 2023, 6:43pm

There’s no resolution for combo meters unless SolarEdge changes how they register meters in the inverter firmware to export data for both functions over modbus instead of picking only one function to export and ignoring the other.

P6Dave · March 23, 2023, 12:16pm

“The default precision setting in HA unfortunately only affects how the HA frontend displays it on cards and stuff, the entity itself doesn’t change precision when used in templates”

I’m not using it in a template though. This is three frontend cards all supposedly displaying the same entity from the integration, only one of which displays it to the level of precision I want ie 1 decimal place.

From the Gauge card:

Screenshot_20230323_121131_Home Assistant

From the Power Distribution Card

Screenshot_20230323_121115_Home Assistant

From the Tesla Style Power Card

Screenshot_20230323_121058_Home Assistant

I wonder if this is a problem with the cards themselves not keeping up with the changes in HA

Maybe I’ll raise an issue with the relevant dev.

Thanks

StijnDW · March 23, 2023, 12:36pm

Complete newbie here - both with coding as HA/any form of automation.

Big thanks for this very elaborate post & dashboard, it’s a great way to get started!

I tried to implement this entire post and I did tackle most of the hurdles by following the thread, but one I’m currently facing is:
The problem: card stating “Entity not available: sensor.solar_imported_power_daily”

The addition of “tariffs” will break the donut “Autarkierate”.
I’ve deleted the tariffs & restarted HA and then it worked.

However, how can I still have the donut working without deleting the tariffs from the energy_utilities.yaml file?

I suppose this one is the forcing me to make a selection: electricity_tariffs_automation.yaml:

Is it possible to make it an optional selector? Or to combine both values in the card and use the sum of both values?

WillCodeForCats · March 23, 2023, 4:19pm

Yes, the custom cards are probably not rounding aware. At least in templates, there is a new flag {{ states('sensor.X', rounded=True) }} that needs to be used to apply the default precision setting.

P6Dave · March 23, 2023, 6:55pm

“a new flag {{ states('sensor.X', rounded=True) }} that needs to be used to apply the default precision”

Oooh! I hadn’t seen that change. I used a simple {{ states('sensor.X') | round (1) }}, which worked.

WillCodeForCats · March 23, 2023, 8:30pm

I don’t know anything about frontend dev to suggest a change for those custom cards, but I would suspect they are missing a flag or argument or function that tells them to reference the default precision setting when displaying sensor entities.

You could make template sensors with the rounded flag that the custom cards reference, but then that’s multiple levels of sensors that gets over complicated to manage. Ideally I would think the custom cards just need an update to be aware of the default precision setting as introduced in HA 2023.3.

ryanm101 · March 24, 2023, 4:23pm

sensor.solar_imported_power_daily_offpeak
sensor.solar_imported_power_daily_peak

sensor.solar_imported_power_daily_<tarriff>

Create a new sensor that is a template:
sensor.solar_imported_power_daily_offpeak + sensor.solar_imported_power_daily_peak

see:

github.com

ryanm101/hasolarcfg/blob/d350c3e3508ad0932bc0b8760f860b00fdc9cb95/packages/electricity_costings.yaml#L18

    
      
            state: >
              {% set peak_cost = (states('sensor.solar_imported_power_daily_peak') | float(0)) * (states('sensor.electricity_peak_tariff') | float(0)) %}
              {{ (peak_cost) | round(2) }}
          - name: "Solar Accounting Offpeak Daily"
            unique_id: solar_accounting_offpeak_daily
            icon: mdi:currency-gbp
            unit_of_measurement: "£"
            state: >
              {% set offpeak_cost = (states('sensor.solar_imported_power_daily_offpeak') | float(0)) * (states('sensor.electricity_offpeak_tariff') | float(0)) %}
              {{ (offpeak_cost) | round(2) }}
          - name: "Solar Accounting Total Daily"
            unique_id: solar_accounting_total_daily
            icon: mdi:currency-gbp
            unit_of_measurement: "£"
            state: >
              {% set compensation = (states('sensor.solar_accounting_peak_daily') | float(0)) + (states('sensor.solar_accounting_offpeak_daily') | float(0)) %}
              {{ (compensation) | round(2) }}
          
          
- name: "Solar Accounting Export Daily"
            unique_id: solar_accounting_export_daily
            icon: mdi:currency-gbp

StijnDW · March 24, 2023, 5:36pm

Big thanks! I added the following and it seems to work!

added to electricity.yaml

template:
  - sensor:
      - name: "Solar Imported Power Daily kWh"
        unique_id: "solar_imported_power_daily_kWh"
        unit_of_measurement: "kWh"
        icon: mdi:transmission-tower-export
        state: >
          {% set imported_power = states('sensor.solar_imported_power_kwh') | float(0) %}
          {% if (is_state('sensor.solar_imported_power_kwh', 'unknown')) %}
            0
          {% else %}
            {{imported_power}}
          {% endif %}
        availability: >
          {{ states('sensor.solar_imported_power_kwh') | is_number}}

I’ve never done this so written based on what else was in the file → any remarks?
Thanks in advance! One step closer to a working dashboard!

ryanm101 · March 24, 2023, 6:15pm

Sorry I didnt read your question properly… Just use:
sensor.solar_imported_power_kwh in Autarkierate
or if you need it to be daily:

template:
  - sensor:
      - name: "Solar Imported Power Daily Total"
        unique_id: "solar_imported_power_daily_total"
        unit_of_measurement: "kWh"
        icon: mdi:transmission-tower-export
        state: >
          {{ states('solar_imported_power_daily_offpeak') | float(0) + states('solar_imported_power_daily_peak') | float(0) }}
        availability: >
          {{ states('sensor.solar_imported_power_kwh') | is_number}}

To my mind it’s an oversight when using tariffs we get two sensors but we should get 3 the third being the total and should use the utility name the same way it does when no tariffs are present. I intend to eventually get round to raising a PR about it.

cannos88 · March 28, 2023, 1:24pm

Is there a way to manually change the type of meter detected? From inverter I configured meter 2 while on HA it detects meter 1

WillCodeForCats · March 31, 2023, 5:04pm

No, the inverter decides how the meter data is presented, not HA or the integration.

Schlichi83 · April 3, 2023, 3:20pm

Hello you all,

I need your help. In January I managed to get a perfect Energy dashboard working using the config without a battery from SgtBatten. Everything worked perfectly.

Today I got a BYD LVS battery installed and I thought I just needed to switch the energy.yaml and everything would work again, but boy was I naive …

There seem to be two versions for a configuration with battery. One in the old thread with an energy.yaml that doesn’t work (anymore?) - at least I don’t see any values in some sensors.
And one that is new that uses several yaml files in the package folder - but that needs a lot of tweaking to actually work.

I have a very regular tariff (0,255€ / kWh) - what do I have to configure?
I read the notes in the github section, but don’t know what to do.

Thank you in advance!

Best regards
Schlichi83

Remko · April 3, 2023, 3:53pm

I would start with using my config from here:

Basically, if you take delete your current config and integration and do a resetup using my config, it would be fairly the same as now, but just at the battery…

You can change the tariff in three energy_tariffs.yaml

But… Make sure you use my fork of the GitHub because that will be very close to your configuration…