Sensors for New Real-Time Power Monitoring in Energy Dashboard

[mastameista]

With HA release 2025.12 Real-Time Power Monitoring has been introduced in energy dashboard. As the power sensors require positive values for importing electricity (grid power) and discharging the battery (battery power), I've inverted the following sensors with a helper (template sensors).

battery power raw (also signed battery power could be used)

{% set v = states('sensor.battery_power_raw') | float %}
  {% if v == 0 %}
    0
  {% else %}
    {{ v * -1 }}
  {% endif %}

export power raw inverted

{% set v = states('sensor.export_power_raw') | float %}
{% if v == 0 %}
  0
{% else %}
  {{ (v * -1) }}
{% endif %}

How did you solve the need for inverted values? Did I miss other types of existing sensors or are there better ways to correctly set up real-time power monitoring?

[mkaiser]

Hi,
I configured the dashboard like this using "meter power" and "Battery power" (I am using the dev-branch, names might deviate from main branch)

The text in the configuration dialogue says
"Pick a sensor which measures grid power in either of GW, kW, mW, MW, TW, W. Positive values indicate importing electricity from the grid, negative values indicate exporting electricity to the grid."
or
"Pick a sensor which measures the electricity flowing into and out of the battery in either of GW, kW, mW, MW, TW, W. Positive values indicate discharging the battery, negative values indicate charging the battery."

so I guess there is no need for additional templates.

Can you double check?

[Gnarfoz]

Please check again when the sun is back up (or just check the sensor history), in 95.10 battery power raw should be negative when charging.

[vordenken]

Just checked again, no negative readings in battery power raw on fw95.10 for me. I have th SH8.0RT20.

[Gnarfoz]

Hm. I vaguely recall that Sungrow did a "change to signed" and "change back to unsigned" flip flop on some register. Perhaps it was this one? Another case example of why it sucks so terribly that there are no firmware changelogs...

[Gnarfoz]

In which case switching to 5214 seems even more important. It would of course break things for everyone currently using battery power raw for anything. We could keep Signed battery power as it is and just offer 5214 as Battery power? Not sure. Thoughts, @mkaiser?

[mp123456-design]

Could you please explain to me noob, how you added the wallbox to your energy monitor? When I try to add it, its not in the devices list.

[mastameista]

Thx @mkaiser!
I thought Meter Active Power is something different. At least I have slightly different values but it might be due to different sensor update times.

I did not use signed battery power because the comment above the sensor says:
positive if charging and negative if discharging

Whilst text in the HA configuration says:
Positive values indicate discharging

But: It looks like signed battery power would work too in my case:

I have firmware version ARM_SAPPHIRE-H_V11_V01_B, MDSP_SAPPHIRE-H_V11_V01_B running.

[mastameista]

I strongly assume, yes.
Battery power raw with newer firmware: #474
The guy has 95.04 and reports the same positive/negative thing. So shall we update the comment?

[Gnarfoz]

I just remembered there's also register 5214 (S32) which also reports battery power, it gives negative values when charging even on 95.01. The documentation actually lists this as preferred over 13022 (U16).
I guess @Tr1n0va was right in #474, but the solution/workaround to use Signed battery power was flawed, because its logic is reversed (like the comment says).
The original error was introduced in the course of #406.
Anyone know someone using a version before 95.01 to check if 5214 is available in such old versions? Maybe someone from Austria, I think they're still stuck on such old versions due to regulations? Or someone using more than 2 SHxRT in master/slave mode?

[mastameista]

don't know anyone. And unfortunately, I'am not that deep into the topic to understand registers, etc.

[mikeharris2017]

I tried to update my SH25T.
It keep telling me I have already the newest version. I can't find anything like 94.0x in the firmware settings. Also Sungrow seems not to provide any (easy to find an use) list of devices and the corresponding firmware.
Which device did you update to 95.0x?

My battery shows:
BAT SBRBCU-S_22011.01.27
WINET WINET-SV300.001.03.P021 > Update available to WINET-SV300.001.03.P024

SH25T:
1 03011.01.31
2 01011.01.31
3 22011.01.27
4 06002.07.17

Cheers.

[Gnarfoz]

95.xy is a SHxRT firmware. SHxT are at 01.xy (as you pointed out). Also, SAPPHIRE is SHxRT, PEARL is SHxT.

[mkaiser]

hi,

this post had a longer text before. Gnarfoz found the error. I committed stuff to the dev branch :)

using the devbranch you can use this sensor for the dashboard:

      # positive if charging, negative if discharging
      - name: Battery charging power signed

[polojoe]

I tried latest dev branch, but sensor.battery_charging_power_signed ist negative when discharging. So not usable for dashboard. My inverter has FW 95.10

Edit: Sensor works as expected.

[Macstar1601]

Why do you not simply create a template sensor helper and multiply the sensor by -1?

{{ (states('sensor.battery_charging_power_signed') | float(0) * -1) }}

[mkaiser]

there were some issues getting the correct data (different behaviour of models / fw-versions).

I hope the new sensor for battery power (reg 5214-5215) is sufficent for all inverter models.

Now these templates are directly in the code and the users don't have to reinvent them for the HA -dashboard:

      
      # positive if charging, negative if discharging
      - name: Battery charging power signed
        unique_id: sg_battery_charging_power_signed
        unit_of_measurement: W
        device_class: power
        state_class: measurement
        availability: "{{ states('sensor.battery_power') not in ['unknown','unavailable'] }}"
        state: "{{ states('sensor.battery_power')|int *-1}}"  # sensor.battery_power is negative when charging

      # positive if charging else zero
      - name: Battery charging power
        unique_id: sg_battery_charging_power
        unit_of_measurement: W
        device_class: power
        state_class: measurement
        availability: "{{ states('sensor.battery_charging_power_signed') not in ['unknown','unavailable'] }}"
        state: >-
          {% if states('sensor.battery_charging_power_signed') |int > 0 %}
            {{ states('sensor.battery_charging_power_signed') |int}}
          {% else %}
            0
          {% endif %}

      # NOTE:
      # Use this sensor for the HA energy dashboard.
      # HA Energy Dashboard configuration description:
      # "Pick a sensor which measures the electricity flowing into and out of the battery in either of GW, kW, MW, mW, TW, W.
      # Positive values indicate discharging the battery, negative values indicate charging the battery."
      #
      # positive if discharging, negative if charging
      - name: Battery discharging power signed
        unique_id: sg_battery_discharging_power_signed
        unit_of_measurement: W
        device_class: power
        state_class: measurement
        availability: "{{ states('sensor.battery_power') not in ['unknown','unavailable'] }}"
        state: "{{ states('sensor.battery_power')|int}}"  # sensor.battery_power is positive when discharging


      # positive if discharging else zero
      - name: Battery discharging power
        unique_id: sg_battery_discharging_power
        unit_of_measurement: W
        device_class: power
        state_class: measurement
        availability: "{{ states('sensor.battery_discharging_power_signed') not in ['unknown','unavailable'] }}"
        state: >-
          {% if states('sensor.battery_discharging_power_signed')|int > 0 %}
            {{ states('sensor.battery_discharging_power_signed')|int }}
          {% else %}
            0
          {% endif %}

The sensor Battery discharging power signed is the sensor to use in the Homeassistant energy dashboard

[Tr1n0va]

But the sensor isn't in the current YAML yet, is it?

[Tr1n0va]

Okay, I briefly tested the dev version and the sensor was there. However, in this version, the “Meter Activ Power” sensor, which is also required for the energy dashboard, is no longer available to me. I then reverted back to the current version. Will the “Meter Active Power” sensor be made available again in the new version?

[mkaiser]

This is strange. I am using the dev branch with the "meter active power" sensor.

Sungrow-SHx-Inverter-Modbus-Home-Assistant/modbus_sungrow.yaml

Line 359 in b0ffffa

- name: Meter active power

After writing some updated documentation, I plan to merge the dev branch into the main branch.

Could you maybe try again and give me some feedback? It would be great to check for "as many hickups as possible" before :)

[Tr1n0va]

Hopefully it will start up again when the sun comes out.

[mkaiser]

If you dont want to wait for the German sun in winter, you could force Charge the Inverter and then Switch to the self consumption mode after a while

[Tr1n0va]

I did that and it worked. It enabled the "Forced Startup Under Low SoC Standby" switch. Everything started up and the battery charged. Does the switch also turn itself off again?

[Tr1n0va]

I mean the „Forced Startup Under Low SoC Standby" switch.

[mkaiser]

honestly, I don't know.
I just let it enabled and I don't know of any possible side effects :)