Massaging battery parameters to use with the Energy Dashboard

[PaulOckenden]

I use an ME3000SP with the solarman_wifikit.yaml definition file.

I tried to add my batteries to HA's energy dashboard, but couldn't because it expects to see in and out values in kWh (evergy), but the output from the ME3000SP is a single charge/discharge instantaneous reading in kW (power). So I had to massage that data into the right format to get it to work.

In case anyone else wants to try, this is how I did it. This is based on stuff I found out there on the Internet, but which didn't work, so I had to make loads of changes. All of this goes into configuration.yaml, by the way.

Firstly, I split the charge/discharge into separate in and out entities using templates:

template:
  - sensor: 
      - name: "batt1 out"
        state: >
          {% if states.sensor.battery1_battery_charge_discharge_power.state | float <= 0 %}
            {{ 0 - states.sensor.battery1_battery_charge_discharge_power.state | float }}
          {% else %}
            0
          {% endif %}
        unit_of_measurement: kW
        device_class: power
        icon: mdi:battery-minus
      - name: "batt1 in" 
        state: >
          {% if states.sensor.battery1_battery_charge_discharge_power.state | float  > 0 %}
            {{ states.sensor.battery1_battery_charge_discharge_power.state | float }}
          {% else %}
            0
          {% endif %}
        unit_of_measurement: kW
        device_class: power
        icon: mdi:battery-plus

You'll see I use batt1 in the code - that's because I have two battery systems. batt2 have essentially the same code duplicated.

You will need to replace battery1_battery_charge_discharge_power with whatever the charge/discharge parameter is called in your system. I think that by default it's solarman_battery_charge_discharge_power.

The next thing I do is use the built in integral facility to sum the kW feed into kWh data:

sensor:
   - platform: integration
    source: sensor.batt1_in
    name: batt1_in_integration
    round: 3
    method: left
  - platform: integration
    source: sensor.batt1_out
    name: batt1_out_integration
    round: 3
    method: left

You may well have an existing sensor: section, if so just add this to the end of that.

Finally, I use the built-in utility meter facility to reset the data on a daily basis:

utility_meter:
  batt1_in_integration_daily:
    source: sensor.batt1_in_integration
    cycle: daily
  batt1_out_integration_daily:
    source: sensor.batt1_out_integration
    cycle: daily

After this, I'm able to use batt1_in_integration_daily and batt1_out_integration_daily to populate the battery fields in the energy dashboard. It won't show correct data until the following day.

I hope someone else finds that useful!

[davidrapan]

I can see that the profile is missing Total Battery Charge and Total Battery Discharge sensors. But I presume the inverter has registers for that?

[PaulOckenden]

Dunno - there's all kinds of buy and sell registers that I think might have been lost in translation! Rather than risking it I thought it was easier to just roll my own from the existing parameter.

However... I have a different (better) Modbus RTU document than the one that generally kicks around, and it suggests that 0x0224 is today's battery in in kWh and 0x0225 is out. I might try adding those to the definition file and see how they correspond to my massaged data.

This is that other file, BTW, in case anyone needs it. sofarhyd-es-me3000sp-modbus-protocol.pdf

[PaulOckenden]

This typo made me laugh:

[davidrapan]

This is that other file, BTW, in case anyone needs it

Great. I add it into the documentation!

This typo made me laugh

😆 Yeah those semi-translated docs are all crazy!

[PaulOckenden]

Hmm... close enough:

That could have saved me a shedload of code!!!!

[PaulOckenden]

(I wish actions in the dev tools accepted hex!)

[davidrapan]

That could have saved me a shedload of code!!!!

Hah!

(I wish actions in the dev tools accepted hex!)

🤔

[PaulOckenden]

567 (0x0237) is useful too - battery health percentage. One of mine shows 100, the other 95.

That better document I added above is like the normal one, but with lots of the "reserved" entries filled in.

[davidrapan]

Sounds good!

It shows you SOH for them individually?

[PaulOckenden]

No, I have two devices:

I ran the 567 read against both of them individually.

I actually have LOADS of batteries. Each ME3000SP has a stack of them. I guess the health is for the stack as a whole.

[davidrapan]

Ah okay, makes sense!

[PaulOckenden]

Hi David, do you think 0x0224, 0x0225, and 0x0237 might make it into an update soon? If so, I'll hold off adding number-based reads in my scripts. No problem if not, though - I don't want to pressure you. I know this isn't a full time job!

[davidrapan]

I added them in feat: Add some missing sensors for sofar and I'll do at least some pre-release soon. 😉