Skip to content

[Feature Request] Separate self-consumption from gridOffPower #65

@fellek

Description

@fellek

Device

SolarFlow 2400 AC + AB3000X

Description

Hi! While comparing the reported gridOffPower value with actual power measurements at the off-grid socket, I noticed that gridOffPower includes the device’s own system losses (inverter, DC/AC converter, BMS, controller) — not just the power delivered to the off-grid consumer.

The difference between reported and measured power varies significantly depending on the device state:

Device state Reported gridOffPower Measured at socket Difference
Discharging (smartMode=1) ~145W ~90W ~50-60W
Charging (smartMode=1) ~120W ~90W ~20-30W
Bypass / SOCEMPTY (smartMode=0) ~95W ~90W ~5W

The attached graph shows this clearly — the gap between reported (blue) and measured (yellow) power shrinks significantly once the device enters bypass mode around 22:20 (SoC reaches minimum).

This makes it difficult for users and integrations to accurately track:

  • How much energy the off-grid consumer actually uses
  • How much energy the device consumes internally
  • The true system efficiency

Request

Would it be possible to expose the device’s internal self-consumption as a separate MQTT property (e.g. selfConsumption in watts)? Since the firmware already seems to know this value — it adds it to gridOffPower — it might be straightforward to report it separately.

Alternatively, reporting the actual power delivered at the off-grid socket (excluding system losses) would also solve the issue. As users could compare battery output with Offgrid-Output.

This would be very helpful for energy monitoring and home automation use cases. Thank you for considering this!

image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions