Native Huawei Support

[Roving-Ronin]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

No native Huawei support

Expected behaviour

Native Huawei support would be nice.

Possible Solutions

If you could give some pointers as to what you require to add support for Huawei, I would be able to look at it to add support to determine the sensors that could be utilised from the Huawei Solar Integration by WLCRS ( https://github.com/wlcrs/huawei_solar ).

Mode

Both

Context / Reason

Provide added support for Huawei users.

[Pho3niX90]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

No native Huawei support

Expected behaviour

Native Huawei support would be nice.

Possible Solutions

If you could give some pointers as to what you require to add support for Huawei, I would be able to look at it to add support to determine the sensors that could be utilised from the Huawei Solar Integration by WLCRS ( https://github.com/wlcrs/huawei_solar ).

Mode

Both

Context / Reason

Provide added support for Huawei users.

What features are you missing, or hoping to see for huawei?

[slipx06]

Hi. That integration will give you most of the required sensors for the card to work. If you can share your card configuration I can add it as an example. If there are specific Huawei Inverter status codes and/or messages please share them.

[Roving-Ronin]

Hi, apologies on slow reply, just busy as atm. Yes I've been working on 'translating' WLCRS entities into the card, however there's some items on the card that don't map to WLCRS / Huawei inverters and also wondering if/how we can add a picture of the Huawei inverters into the card, same as like GoodWe etc have been added?

If I can map out the corresponding entities for Huawei in the card, is there somewhere to publish them or would this be added into the code so if a user has something like this in the yaml, it would show the Huawei inverter image ?

inverter:
  modern: false
  colour: grey
  autarky: energy
  model: huawei_gridmode
  three_phase: true

Also wondering if anyone has looked at supporting multiple inverters in the card? May not be space for 2 inverter images, but more instead of 4 MPTT on 1 inverter in the card, if you could have 2 MPTT per inverter (maybe option to different colour per inverter data) and additional entries for 2nd inverter internal temperature / status / autarky / inverter Amps and Active Power etc.

[slipx06]

Hi. If you share an image of the inverter I can add together with the model tag. What is the significance of the appended "gridmode". I would have assumed just model: huawei . You will also need to share the inverter_status messages for mapping.

I don't think support for multiple inverters will be possible without a complete redesign. Maybe there is a way for you to have two separate cards to depict this.

[Roving-Ronin]

Hi @slipx06, th

The 'gridmode' was just from mymicing the GoodWe inverter config that has that, ignore/delete it in regards Huawei. For the residential sizes Huawei inverters, the current range looks like:

or if you need a dark background:

Will revert re the mappings, need to get a chance to do some more testing.

[kurtdefeyter]

Very interested in this ,

my setup
SUN2000-8KTL-M1
luna 2000 15 kw
22 optimizers

Please contact me and let me know how i can help

[Roving-Ronin]

@kurtdefeyter
Can you send me your LUNA ESS, to allow testing ? I'll send you a pre-paid mailbag ;-)

a) Do you have WLCRS integration for Huawei installed ? If not see: https://github.com/wlcrs/huawei_solar

b) If/once you have WLCRS installed, could you lookup ALL the battery entities that is creates ? Open up the entity and copy the raw e.g. 'sensor.battery_state_of_capacity_1' (or does it not add the _1 if there's only 1 ESS?) and all the other sensor for the LUNA ESS ? Below is the entities its supposed to have... but there might be more that are not enabled in HA by default (handy to list them also).

c) I assume you have a single inverter, could you also confirm the entity naming structure WLCRS uses by default, as I have a couple of inverters and have changed the format of mine to make more sense.

iirc I think your inverter Input for the panels would have: sensor.inverter_pv_1_voltage or is it sensor.inverter_pv_voltage_1 ?

[kurtdefeyter]

hi nice to meet you,
I have it connected with all possible ways described in the connection document
https://github.com/wlcrs/huawei_solar/wiki/Connecting-to-the-inverter

[kurtdefeyter]

the inventor looks like this

The input sensors

[Roving-Ronin]

@slipx06 is this to type of information that you require, to allow the card to understand the Huawei status / state and grid status codes?

https://github.com/wlcrs/huawei-solar-lib/blob/master/src/huawei_solar/register_values.py

i.e. sensor.inverter_device_status appears to have any of these for status message:

Name: Device Status
Entity: sensor.inverter1_device_status

"Standby: initializing",
"Standby: detecting insulation resistance",
"Standby: detecting irradiation",
"Standby: grid detecting",
"Starting",
"On-grid",
"Grid Connection: power limited",
"Grid Connection: self-derating",
"Off-grid mode: running",
"Shutdown: fault",
"Shutdown: command",
"Shutdown: OVGR",
"Shutdown: communication disconnected",
"Shutdown: power limited",
"Shutdown: manual startup required",
"Shutdown: DC switches disconnected",
"Shutdown: rapid cutoff",
"Shutdown: input underpowered",
"Grid scheduling: cosphi-P curve",
"Grid scheduling: Q-U curve",
"Grid scheduling: PF-U curve",
"Grid scheduling: dry contact",
"Grid scheduling: Q-P curve",
"Spot-check ready",
"Spot-checking",
"Inspecting",
"AFCI self check",
"I-V scanning",
"DC input detection",
"Running: off-grid charging",
"Standby: no irradiation",

=============================

Name: Inverter State
Entity: sensor.inverter1_inverter_state

0b0000_0000_0000_0001: "Standby",
0b0000_0000_0000_0010: "Grid-Connected",
0b0000_0000_0000_0100: "Grid-Connected normally",
0b0000_0000_0000_1000: "Grid connection with derating due to power rationing",
0b0000_0000_0001_0000: "Grid connection with derating due to internalcauses of the solar inverter",
0b0000_0000_0010_0000: "Normal stop",
0b0000_0000_0100_0000: "Stop due to faults",
0b0000_0000_1000_0000: "Stop due to power rationing",
0b0000_0001_0000_0000: "Shutdown",
0b0000_0010_0000_0000: "Spot check",

Is what is in the py code, but looking at my inverter its only had 'Standby' (currently as its 3am here) and during the day 'Grid-Connected, Grid-Connected normally'. Based upon that and the grouping of the options above by the 0000_0000 pattern in front it looks like the options are:

"Standby",
"Grid-Connected",
"Grid-Connected, Grid-Connected normally",
"Grid-Connected, Grid connection with derating due to power rationing",
"Grid connection with derating due to internalcauses of the solar inverter",
"Normal stop",
"Stop due to faults",
"Stop due to power rationing",
"Shutdown",
"Spot check",

=============================

Name: Battery Status
Entity: sensor.battery_status

Options:

OFFLINE
STANDBY
RUNNING
FAULT
SLEEP_MODE

=============================

Not sure about this, if I could find out the sensor entiry it is published as AND if it equates to being able to use this as the current working mode (flow direction) of the battery.

class StorageForcibleChargeDischarge(IntEnum):
"""Storage Product Model."""

Options:
STOP
CHARGE
DISCHARGE

[Roving-Ronin]

@kurtdefeyter how are you billed for your electricity ? i.e. Time of Use with set times of the day/night and/or specific days that different tariffs apply? Do you get paid for electricity you export back into the grid / how much (flat rate or varies)?

I still have to group up all the sensors / energy_meters and utility_meters a Huawei users needs to add in atop WLCRS, but you might want to start by making a huawei_derived_sensors.yaml file and place it in the /packages directory, copy this following into it and reload HA.

template:

#############################
#   
#   If your HA instance has a /config/packages directory configured, this may be deployed by saving this text into a file
#   in that location. i.e.   /config/packages/huawei_derived_sensors.yaml
#


  # Shows the calculated current load being consumed by the household, in Watts
  - sensor:
    - name: "House Consumption Power"
      unique_id: house_consumption_power
      unit_of_measurement: "W"
      icon: mdi:solar-power
      device_class: "power"
      state_class: measurement
      state: >-
        {% set inv_active_power = states('sensor.inverter_active_power')|float(0) %}
        {% set pm_active_power = states('sensor.power_meter_active_power')|float(0) %}
        {{ (inv_active_power - pm_active_power)|float(0)|round(0) }}
      availability: >-
        {{ (states('sensor.inverter_active_power')|is_number)
            and (states('sensor.power_meter_active_power')|is_number) }}

#############################

To get the Daily Import / Export kWh totals, I'll send the file later (need your electricity how billed info first), But you might want to install https://github.com/zeronounours/HA-custom-component-energy-meter that gives you the Energy_Meter (like Utility_Meter but supports working out the costs and storing costs paid for kWh import / export

[kurtdefeyter]

We do have a dynamic contract , so the price we pay is based on the Belpex
the calculation is this part of Belgium is actually
{% set s = { "bijz_accijns": 0.014416, "energiebijdrage": 0.0020417, "groenestroom_wkk": 0.02184, "kwh_tarief": 0.0374193, "VAT": 1.06, "marge": 0.002040 } %} {{((current_price + s.marge) * s.VAT + s.bijz_accijns + s.energiebijdrage + s.groenestroom_wkk + s.kwh_tarief) | float}}

the daily result looks like

Yes we do get paid for the injection , this is also based on the Belpex price

https://transparency.entsoe.eu/transmission-domain/r2/dayAheadPrices/show?name=&defaultValue=true&viewType=GRAPH&areaType=BZN&atch=false&dateTime.dateTime=25.11.2023+00:00|CET|DAY&biddingZone.values=CTY|10YBE----------2!BZN|10YBE----------2&resolution.values=PT15M&resolution.values=PT30M&resolution.values=PT60M&dateTime.timezone=CET_CEST&dateTime.timezone_input=CET+(UTC+1)+/+CEST+(UTC+2)

[Roving-Ronin]

Umm yeah ok, talk about overly complicated. Has someone already released an integration for HA, that provides you with an entity of the current price to buy and sell power ?

No idea who the Belgium power retailers are but UK example iirc is Octopus, in Australia there is Amber ... look them up in HACS and you'll see they have e an integration that allows pulling 5min update prices as they resell wholesale market prices.

See:

https://doe-duurzaam.nl/artikel/dynamische-energieprijzen-inlezen-met-home-assistant-zo-doe-je-dat/

???

Or this one that supports Belgium prices : https://github.com/custom-components/nordpool

[kurtdefeyter]

sure this is the calculation template based on the entsoe intagration however i have many costumers that are using it with nordpool to .

We post our templates on https://github.com/JaccoR/hass-entso-e/discussions/categories/price-modifyer-templates

[Roving-Ronin]

@slipx06 @kurtdefeyter

OK I think I've worked out most of the mappings / Huawei equivalents, I've just got to work out the best way of defining the extra sensors that WLCRS doesn't create by default (i.e. the Daily Export / Import totals) and try and ensure they align with other addons/integrations.. oh and also the p/kWh import costs / export sell price (I use a sensor that tracks day and time and switches automatically as per our Time of Use plan in Australia, but Kurt provides an example of way complex plans that EU has.... thinking it might just be a case of BYO for that sensor).

Here's my current setup, ignore the reference to IoTaWatt, its just providing some of the sensors (lights, HVAC, GPOs etc) whilst the servers / network gear is provided by Athom ESP plugs.

Exporting KWh back to the Grid - correct export price also shows.

Importing kWh from the Grid - correct import price also shows.

Only thing missing at the moment, apart from the battery specific sensors that @kurtdefeyter will need to test (since I don't have a battery) is the inverter status information, that currently the card doesn't understand hence no green/red next to the inverter status and the Grid icon showing as Off Grid.

Here's the yaml as it stands currently (but my servers etc sensors reverted back to the geyser sensor etc).

type: custom:sunsynk-power-flow-card
cardstyle: full
panel_mode: false
large_font: false
title: Huawei Power Flows
title_colour: White
title_size: 18px
show_solar: true
show_battery: true
decimal_places: 3
inverter:
  modern: true
  colour: grey
  autarky: power
  auto_scale: true
  model: huawei
  three_phase: true
battery:
  energy: 15000
  shutdown_soc: 20
  invert_power: false
  colour: pink
  show_daily: true
  animation_speed: 6
  max_power: 5000
  full_capacity: 80
  empty_capacity: 10
  show_absolute: false
  auto_scale: true
solar:
  colour: orange
  show_daily: true
  mppts: 2
  animation_speed: 9
  max_power: 13200
  pv1_name: North
  pv2_name: East
  pv3_name: West
  pv4_name: South
  auto_scale: true
  display_mode: 2
load:
  colour: '#5fb6ad'
  show_daily: true
  show_daily_aux: true
  show_aux: true
  invert_aux: false
  show_absolute_aux: false
  aux_name: Generator
  aux_type: gen
  aux_colour: green
  aux_off_colour: red
  aux_loads: 2
  aux_load1_name: Aux load 1
  aux_load2_name: Aux load 2
  aux_load1_icon: mdi:air-filter
  aux_load2_icon: mdi:stove
  animation_speed: 8
  essential_name: Essential
  max_power: 8000
  additional_loads: 2
  load1_name: Geyser
  load2_name: Pool
  load3_name: Spare
  load4_name: Spare
  load1_icon: boiler
  load2_icon: mdi:pool
  load3_icon: mdi:water-boiler
  load4_icon: mdi:lightbulb
  auto_scale: true
grid:
  colour: '#5490c2'
  export_colour: brown
  show_daily_buy: true
  show_daily_sell: true
  no_grid_colour: '#a40013'
  show_nonessential: true
  invert_grid: true
  nonessential_name: Non Essential
  nonessential_icon: oven
  additional_loads: 3
  load1_name: Load 1
  load2_name: Load 2
  load3_name: Load 3
  load1_icon: boiler
  load2_icon: mdi:ev-station
  load3_icon: mdi:lightbulb
  animation_speed: 8
  max_power: 8000
  auto_scale: true
entities:
  use_timer_248: false
  priority_load_243: switch.sunsynk_toggle_priority_load
  day_battery_discharge_71: sensor.battery_day_discharge
  day_battery_charge_70: sensor.battery_day_charge
  day_load_energy_84: none
  day_grid_import_76: none
  day_grid_export_77: none
  day_pv_energy_108: sensor.inverter_total_daily_yield
  day_aux_energy: none
  inverter_voltage_154: sensor.power_meter_phase_a_voltage
  inverter_voltage_L2: sensor.power_meter_phase_b_voltage
  inverter_voltage_L3: sensor.power_meter_phase_c_voltage
  load_frequency_192: sensor.power_meter_frequency
  inverter_current_164: sensor.inverter_phase_a_current
  inverter_current_L2: sensor.inverter_phase_b_current
  inverter_current_L3: sensor.inverter_phase_c_current
  inverter_power_175: sensor.inverter_active_power
  inverter_status_59: sensor.inverter_inverter_state
  radiator_temp_91: null
  dc_transformer_temp_90: sensor.inverter_internal_temperature
  pv1_power_186: sensor.inverter_input_power1
  pv2_power_187: sensor.inverter_input_power2
  pv3_power_188: none
  pv4_power_189: none
  remaining_solar: sensor.energy_production_today_remaining
  total_pv_generation: sensor.inverter_total_yield
  pv1_voltage_109: sensor.inverter_pv1_voltage
  pv1_current_110: sensor.inverter_pv1_current
  pv2_voltage_111: sensor.inverter_pv2_voltage
  pv2_current_112: sensor.inverter_pv2_current
  pv3_voltage_113: none
  pv3_current_114: none
  pv4_voltage_115: none
  pv4_current_116: none
  battery_voltage_183: sensor.battery_bus_voltage
  battery_soc_184: sensor.battery_state_of_capacity
  battery_power_190: sensor.battery_charge_discharge_power
  battery_current_191: sensor.battery_bus_current
  battery_status: null
  battery_temp_182: sensor.battery_temperature
  essential_power: sensor.house_consumption_power
  essential_load1: sensor.tuya_geyser_current_consumption
  essential_load2: sensor.load2_power
  load_power_L1: null
  load_power_L2: null
  load_power_L3: null
  nonessential_power: sensor.sunsynk_power_flow_non_essential_active_power
  non_essential_load1: sensor.nonessential1_power
  non_essential_load2: sensor.nonessential2_power
  non_essential_load3: sensor.nonessential3_power
  grid_power_169: sensor.house_consumption_power
  grid_ct_power_172: sensor.power_meter_phase_a_active_power
  grid_ct_power_L2: sensor.power_meter_phase_b_active_power
  grid_ct_power_L3: sensor.power_meter_phase_c_active_power
  grid_ct_power_total: sensor.power_meter_active_power
  grid_connected_status_194: sensor.inverter_off_grid_status
  aux_power_166: sensor.sunsynk_aux_power
  aux_connected_status: binary_sensor.sunsynk_aux_connected_status
  aux_load1: sensor.gesyer
  aux_load2: sensor.pool_pump
  aux_load1_extra: sensor.daily_geyser_energy
  aux_load2_extra: sensor.pool_temperature
  prog1_time: sensor.sunsynk_time_slot_1
  prog1_capacity: number.sunsynk_system_mode_soc_time1
  prog1_charge: switch.sunsynk_system_mode_grid_charge_time1
  prog2_time: sensor.sunsynk_time_slot_2
  prog2_capacity: number.sunsynk_system_mode_soc_time2
  prog2_charge: switch.sunsynk_system_mode_grid_charge_time2
  prog3_time: sensor.sunsynk_time_slot_3
  prog3_capacity: number.sunsynk_system_mode_soc_time3
  prog3_charge: switch.sunsynk_system_mode_grid_charge_time3
  prog4_time: sensor.sunsynk_time_slot_4
  prog4_capacity: number.sunsynk_system_mode_soc_time4
  prog4_charge: switch.sunsynk_system_mode_grid_charge_time4
  prog5_time: sensor.sunsynk_time_slot_5
  prog5_capacity: number.sunsynk_system_mode_soc_time5
  prog5_charge: switch.sunsynk_system_mode_grid_charge_time5
  prog6_time: sensor.sunsynk_time_slot_6
  prog6_capacity: number.sunsynk_system_mode_soc_time6
  prog6_charge: switch.sunsynk_system_mode_grid_charge_time6
  energy_cost_buy: sensor.electricity_price
  energy_cost_sell: input_number.electricity_export_rate
  solar_sell_247: switch.sunsynk_toggle_solar_sell

@kurtdefeyter could you check the sensors here and 'convert' the sensors that I have based upon multiple inverters, into your single inverter sensor names? I've tried to enter them as I think a single inverter sensor naming format is by default, but they need checking. For example here's what my config has, 2 x 6kW M1 inverters, each with MPTT #1 having a single 19 panel string attached (nothing on MPTT @2), hence my config I use pv1 to represent the primary inverter string and pv2 to represent the secondary inverter string.

pv1_power_186: sensor.inverter1_input_power
pv2_power_187: sensor.inverter2_input_power

total_pv_generation: sensor.inverter1_total_yield
pv1_voltage_109: sensor.inverter1_pv_1_voltage
pv1_current_110: sensor.inverter1_pv_1_current
pv2_voltage_111: sensor.inverter2_pv_1_voltage
pv2_current_112: sensor.inverter2_pv_1_current

Hopefully this is a good start.

[Roving-Ronin]

@slipx06
D'Oh that seems to have broken it all :-(
Trying to work out what is wrong and all I can see is, is the ' supposed to be a ` ?

As in when that status mess was in:

        alarm: {
            states: ['Grid-Connected, Grid connection with derating due to power rationing', `Grid-Connected, Grid connection with derating due to internal causes of the solar inverter` ], 
            color: 'orange', message: localize('common.alarm')

the first error message is defined by ' at the start and end, and the second status message has ` at the start and end.

Where as in the 4.10.3 we have updated it to:

    huawei: {
        standby: {states: ['Standby'], color: 'blue', message: localize('common.standby')},
        selftest: {states: ['Spot check'], color: 'yellow', message: localize('common.selftest')},
        normal: {states: ['Grid-Connected, Grid-Connected normally', 'Grid-Connected, Grid connection with derating due to power rationing'], color: 'green', message: localize('common.normal')},
        shutdown: {states: ['Shutdown'], color: 'red', message: localize('common.shutdown')},
        normalstop: {states: ['Normal stop'], color: 'yellow', message: localize('common.normalstop')},
        alarm: {
            states: [`Grid-Connected, Grid connection with derating due to internal causes of the solar inverter` ], 
            color: 'orange', message: localize('common.alarm')
        },
        fault: {states: ['Stop due to faults', 'Stop due to power rationing'], color: 'red', message: localize('common.fault')},
    },

That has both the status messages for the 'normal definition, being found with ' at the start/end of each... should the second message have instead ? Also the alarm message has at the start/end, whereas all the other definitions with only one status message as an option use ' at the start/end of the message?

[slipx06]

I've pushed a fix. Please test

[Roving-Ronin]

@slipx06 no that doesn't appear to work either.

4.10.2 worked fine, just that we're trying to move Grid-Connected, Grid connection with derating due to internal causes of the solar inverter from being an alarm type message, to being a normal type status message.

i.e. so normal can be either of 'Grid-Connected, Grid-Connected normally' or Grid-Connected, Grid connection with derating due to internal causes of the solar inverter. Wilst the alarm message options shrinks to only have the one message option, that being Grid-Connected, Grid connection with derating due to internal causes of the solar inverter

PS. Apologies for all the hassle.

[slipx06]

OK I see the issue. Pushed another version to test

[Roving-Ronin]

@slipx06 Thanks version is working now. Appreciated. Hopefully will have mapping list (with battery) and extra items to allow copy/paste for Huawei users to setup.

[Roving-Ronin]

@slipx06 Apologies but I'm not having any luck working out how to create examples in the documentation for Huawei. Would you be able to setup a page for this, probably looking at examples for:

a) 1 x L1 1phase inverter with 15kWh LUNA ESS battery - 2 PV strings.
b) 2 x L1 1phase inverter with 15kWh LUNA ESS battery - 4 PV strings (2 per inverter) and Primary inverter used for temp etc.
c) 1 x M1 3phase inverter with 15kWh LUNA ESS battery - 2 PV strings.
d) 2 x M1 3phase inverter with 15kWh LUNA ESS battery - 4 PV strings (2 per inverter) and Primary inverter used for temp etc.

I would assume users should be able to work out from that if they don't have a battery, how to disable it in the card etc.

... then the additional derived sensors that users need to create in HA, from the standard WLCRS integration from Huawel, to cater for mulitple inverters combined values, daily kW/h usage/export totals, AUX and Non-Essential Power/Energy totals etc.

For 'solar_sell_247' trying to work out if there's a call for this for Huawei and if so, if/how to setup a switch that calls a WLCRS added service to change the Power Feed to Grid to Maximum (i.e. Sell) or Zero (i.e. Don't sell)

Debating including examples of sensors to define the current electricity costs (or compensation from exporting kWh), that are then used in the card, or (most probably) including a link to the WLCRS integration Wiki ( https://github.com/wlcrs/huawei_solar/wiki - new page to add under here).

To start, here's the 2 x Huawei L1 (1phase) with 1 x 15kWh LUNA ESS battery - 4 PV strings:

type: custom:sunsynk-power-flow-card
cardstyle: full
panel_mode: false
large_font: false
title: Huawei Power Monitor
title_colour: White
title_size: 18px
show_solar: true
show_grid: true
show_battery: true
decimal_places: 2
inverter:
  modern: false
  colour: grey
  autarky: power
  auto_scale: true
  model: huawei
  three_phase: false
battery:
  energy: 14850
  shutdown_soc: 15
  invert_power: true
  colour: pink
  show_daily: true
  animation_speed: 5
  max_power: 5000
  show_absolute: false
  auto_scale: true
  hide_soc: false
  show_remaining_energy: false
solar:
  colour: '#5fb6ad'
  show_daily: true
  mppts: 4
  animation_speed: 8
  max_power: 13200
  pv1_name: Inv.1 PV1
  pv2_name: Inv.1 PV2
  pv3_name: Inv.2 PV1
  pv4_name: Inv.2 PV2
  display_mode: 2
load:
  colour: magenta
  show_daily: true
  show_daily_aux: true
  show_aux: true
  invert_aux: false
  show_absolute_aux: false
  aux_name: Generator
  aux_type: gen
  aux_colour: green
  aux_off_colour: brown
  aux_loads: 2
  aux_load1_name: IT - Servers
  aux_load2_name: IT - Network
  aux_load1_icon: mdi:server-network
  aux_load2_icon: mdi:network
  animation_speed: 4
  essential_name: Essential
  max_power: 4000
  additional_loads: 2
  load1_name: Lights
  load2_name: All GPO
  load3_name: Spare
  load4_name: Spare
  load1_icon: mdi:lightbulb
  load2_icon: mdi:power-plug
  load3_icon: mdi:water-boiler
  load4_icon: mdi:kettle
  auto_scale: true
  dynamic_icon: true
  dynamic_colour: true
grid:
  colour: red
  export_colour: '#5490c2'
  show_daily_buy: true
  show_daily_sell: true
  no_grid_colour: '#a40013'
  show_nonessential: true
  invert_grid: true
  nonessential_name: Non Essential
  nonessential_icon: none
  additional_loads: 2
  load1_name: HVAC
  load2_name: EV
  load1_icon: mdi:fan
  load2_icon: mdi:car
  animation_speed: 7
  max_power: 10000
  auto_scale: true
  dynamic_icon: true
  dynamic_colour: true
  energy_cost_decimals: 3
entities:
  use_timer_248: null
  priority_load_243: null
  day_battery_charge_70: sensor.battery_day_charge
  day_battery_discharge_71: sensor.battery_day_discharge
  day_load_energy_84: sensor.house_consumption_energy_less_known
  day_grid_import_76: sensor.hs_grid_imported_daily
  day_grid_export_77: sensor.hs_grid_exported_daily
  day_pv_energy_108: sensor.inverters_total_daily_yield
  day_aux_energy: sensor.sunsynk_power_flow_card_aux_devices_energy
  inverter_voltage_154: sensor.power_meter_voltage
  load_frequency_192: sensor.power_meter_frequency
  inverter_current_164: sensor.inverter_phase_a_current
  inverter_power_175: sensor.inverters_active_power
  inverter_status_59: sensor.inverter_inverter_state
  radiator_temp_91: null
  dc_transformer_temp_90: sensor.inverter_internal_temperature
  pv1_power_186: sensor.inverter_pv_1_power
  pv2_power_187: sensor.inverter_pv_2_power
  pv3_power_188: sensor.inverter_pv_1_power_2
  pv4_power_189: sensor.inverter_pv_2_power_2
  environment_temp: sensor.<your_location>_temp
  remaining_solar: sensor.energy_production_today_remaining
  total_pv_generation: sensor.inverter_total_yield
  pv1_voltage_109: sensor.inverter_pv_1_voltage
  pv1_current_110: sensor.inverter_pv_1_current
  pv2_voltage_111: sensor.inverter_pv_2_voltage
  pv2_current_112: sensor.inverter_pv_2_current
  pv3_voltage_113: sensor.inverter_pv_1_voltage_2
  pv3_current_114: sensor.inverter_pv_1_current_2
  pv4_voltage_115: sensor.inverter_pv_2_voltage_2
  pv4_current_116: sensor.inverter_pv_2_current_2
  battery_voltage_183: sensor.battery_bus_voltage
  battery_soc_184: sensor.battery_state_of_capacity
  battery_power_190: sensor.battery_charge_discharge_power
  battery_current_191: sensor.battery_bus_current
  battery_temp_182: sensor.battery_temperature
  battery_status: sensor.battery_status
  essential_power: sensor.house_consumption_power_less_known
  essential_load1: sensor.all_lights_active_power
  essential_load2: sensor.gpo_all_active_power_less_known
  essential_load1_extra: null
  essential_load2_extra: null
  load_power_L1: null.3phase_only
  load_power_L2: null.3phase_only
  load_power_L3: null.3phase_only
  nonessential_power: sensor.sunsynk_power_flow_non_essential_active_power
  non_essential_load1: sensor.aircon_active_power
  non_essential_load2: sensor.ev_charger_active_power
  grid_power_169: sensor.house_consumption_power
  grid_ct_power_172: sensor.power_meter_active_power
  grid_ct_power_total: sensor.power_meter_active_power
  grid_connected_status_194: sensor.inverter_off_grid_status
  aux_power_166: sensor.sunsynk_power_flow_aux_devices_active_power
  aux_connected_status: binary_sensor.sunsynk_aux_connected_status
  energy_cost_buy: sensor.electricity_price
  energy_cost_sell: sensor.electricity_fit
  solar_sell_247: switch.null
  aux_load1: sensor.it_hardware_network_active_power
  aux_load2: sensor.it_hardware_servers_active_power
  aux_load1_extra: sensor.env_network_rack_bme280_temperature
  aux_load2_extra: sensor.env_server_rack_bme280_temperature
  grid_voltage: sensor.power_meter_voltage

Note: I haven't defined the:

  prog1_time: sensor.sunsynk_time_slot_1
  prog1_capacity: number.sunsynk_prog1_capacity
  prog1_charge: switch.sunsynk_prog1_grid_charge

as whilst Huawei has the ability to define (and read via Modbus / WLCRS integration) 'Time of Use Periods' and 'Fixed Charging Periods' these are made available as attributes in the sensors, where as I assume the card / for Sunsynk inverters expects this to be individual senors for each time period?

(Based upon the times I'm guessing the + vs - at the end of these periods means charge vs discharge).

[slipx06]

@Roving-Ronin Ive added the example section to populate

https://slipx06.github.io/sunsynk-power-flow-card/examples/huawei.html

[Roving-Ronin]

@slipx06 I've just submitted a pull request for this. Still just needing to add some example tariff plan yaml though. I've created a sub folder in the examples to hold the huawei example yaml files.

As I'm working off my Fork of your repository (so I can make edits and only merge when ready), added a discussion section (in addition to the 'Issues' section is has by default), thinking that instead of clogging up your discussions with Huawei / iStore (fyi in Australia Huawei is now being resold via a partner as iStore) 'can you fix this' or 'can you add that' that people can do that there. Which will also allow them to then use the example yamls from there to test (as they'll be the BETA versions), prior to them merging with your repository (i.e. GA versions).

Thinking as I type... would it be a good idea to add a 'Section' in your Discussion area for "Specific Vendor Support" and then creating 'Categories' within that for the various inverter brands now supported? i.e. Sunsynk, Deye, Solis, Lux, FoxESS, Goodwe, Huawei / iStore, Victron etc? Then in the Huawei / iStore just put a comment for issues/changes/requests etc refer to https://github.com/Roving-Ronin/sunsynk-power-flow-card/discussions ?

[slipx06]

Thanks for the support suggestion. I've added the new section and categories.

[Roving-Ronin]

@slipx06 thought you might be interested in this, to allow creating animated GIFs on the readme page (or when trying to show how to do something / how card should be working in a discussion/issue thread), have a look at this free and without watermarks etc app. https://www.screentogif.com/. Easy as to use, just place frame around area on desktop to record, click record button and then 'save as'.

[slipx06]

Thanks for the tip. I've been using LiceCap https://www.cockos.com/licecap/

[Roving-Ronin]

Hi @slipx06

Could you please confirm (or point me to where they are defined / which file in the card code) the colour codes assigned to the battery status? Just looking at the instance of the gent that is generous to provide me with access to his battery for checking yaml and noticed his battery has a fault and is reporting offline.

I would have thought that 'Offline' would earn a red status light, not a Yellow one?

Also looking at the inverter and notice that its showing with a Green icon and 'Normal' status. This would be as inverter_status_59 is looking at the Inverter(s) 'Device Status', where as the issue for the child device (battery) is flagged in the Inverter(s) 'Alarms' sensor.

Interested in your thoughts... do the other inverters your used to show the alarms and everything such as that within the inverter 'status' sensor? Would you suggest needing to update the Huawei InverterS (the derived sensor version) to somehow say if <insert the current 'normal' status messages we have coded in> then report normal, "else if" status = BUT then merge in the 'sensor.inverters_alarms" state so the inverter(s) status sensor would have

    huawei: {
        standby: {states: ['Standby'], color: 'blue', message: localize('common.standby')},
        selftest: {states: ['Spot check'], color: 'yellow', message: localize('common.selftest')},
        normal: {states: ['Grid-Connected, Grid-Connected normally', 'Grid-Connected, Grid connection with derating due to power rationing'], color: 'green', message: localize('common.normal')},
        shutdown: {states: ['Shutdown'], color: 'red', message: localize('common.shutdown')},
        normalstop: {states: ['Normal stop'], color: 'yellow', message: localize('common.normalstop')},
        alarm: {
            states: [`Grid-Connected, Grid connection with derating due to internal causes of the solar inverter`, 'INSERT DERIVED SENSOR STATES HERE THAT ADD IN THE INVERTER ALARM SENSOR MESSAGES ], 
            color: 'orange', message: localize('common.alarm')
        },
        fault: {states: ['Stop due to faults', 'Stop due to power rationing'], color: 'red', message: localize('common.fault')},
    },

See page 82 / Section 5.1 for the Alarm Codes. Solar Inverter Modbus Interface Definitions - 2023-02-16 v05 SPC158.pdf

Would have to double check, but appears to be that WLCRS presents this in the format of:
[Alarm Level - i.e. Major/Minor/Warning] AlarmID#: Alarm Name

i.e. [Minor] 0268: Battery Abnormal

[Roving-Ronin]

Hi @slipx06

I'm trying to 're-do' the Huawei sensors and mapping of sensors to the card, given updates to your code and also the updates to the WLCRS Huawei Intergration (in testing at v1.4.0a3 currently).

As part of that will be trying to re-work it to more closely align with the default powr flows of the card (as far as Huawei tech / software allows). i.e.:

#280 (comment)

#280 (comment)

I'll post any questions / issues that arise as I go below, but the first issue I've run into is:

1. The Battery 'Optional Sensor' for the (battery) Energy, that allows using a sensor appears to be reading the sensors as Watts only?
   If so this is an issue, as in HA there device_class for batteries is 'SensorDeviceClass.ENERGY_STORAGE' and it allows supported units of "Wh, kWh, MWh, MJ, GJ".

Given this I have a sensor for the total rated batteries capacity, that will automatically calculate the size of all the battery modules in kWh. So currently it is showing a battery stack of 2 x 5000W unit, as a rated capacity of 10kWh. Using this sensor in the card, it shows as 0.01 kWh capacity. So in other words the card logic is assuming any sensor is in Watts, could this be updated to support the official units in HA (or at least kWh and Wh.... given the crazy prices of batteries I think we don't have to worry about a sensor with MWh for a while) ;-)

2. For Essential Load, when using all Essential Load 1 - 4, I note that the name tags of 1-2 are are under the boxes, whilst 3-4 are under them. Wondering if all these names should be on the 'outside' of the boxes (i.e. 1-2 on the top and 3-4 under) that would allow for space inside of the boxes (closest the house icon) for all Essential Loads to have Essential Load Extras?. So would look like this (ignore all daily kWh examples are the same..quick copy / paste):

3. If displaying the grid cost it is aligned left of the power line come out of the grid plyon, when also using the non_essential_load2_extra (to display total kWh it used today) this is aligned to be on the outside oof the non_essential_load2 box and extend right. This causes these two items to overlap each other.

Would it be possible that non_essential_load1_extra instead is located just left of the power line (or above the W in 18W) and extended to the left, and the non_essential_load2_extra is aligned to the right of the power line (or just left a bit of the 3 in 3W) and extends right. Whilst the price for power above the grid icon is maybe to the right of the pylon, or even better if it could be split so the $ 0.xxxx is left of the power line and maybe with the $/kWh below the numbers? Like:

[slipx06]

I'll take a look

[Roving-Ronin]

@slipx06

Using 4.38 (Full card) and found that if I turn off the AUX being displayed, that he Daily Energy kWh for Essential jumps to the right, see:

---

Also wondering, as we already have Essential / AUX / Grid with their Daily kWh counters displayed, would it be possible to have this also for Non-Essential ? Maybe like:

---

Looking at the card, updated with different sensors to follow the SunSynk flows, I noticed that the 'Dynamic Colour' functionality doesn't extend to the 'box showing Hz / V / kW' or the 'Non Essential' boxes. Any chance that the dynamic colour function could be extended to there? I assume this would mean dividing the line / hiving off the line going to the grid so it and the non-essential are treated seperated from each other, so grid would be either (default colours for export/import) green or red and then the boxes and lines from the right of the inverter box, would be able to show the dynamic colour of their power source(s).

'Flow balls' would then also be able to reflect power coming from solar/battery vs 'flow balls' also coming from the grid. Currently, as below, even though the bulk of the power going into Non-Essential (EV) is from the Inverter side, the flow balls show it as if its all coming from the grid.

Or else in the above situation the ball is flowing into the inverter box, when in fact it should really be flowing from the inverter box, as 5kW is coming from the inverter, whilst 2kW is from the grid, to give the 7kW into the Non-Essential / EV charger.

---

Lastly re: #280 (comment) and the logic of

"2 = 4 - 3
5 = 1 + 2 - 6"

Are 2 and 5 automatically calculated within the card, if the others are provided?
If not and needing to provide a custom sensor to calculate this, looking at 2 = 4 - 3. For the Hauwei 4 (grid) is natively a negative for importing, whilst 3 is a positive for consumption, so '2 = -4 - 3' ends up incorrect, so in the custom sensor we have to use '2 = 4 + 3'. Would this cause any issues your aware of in the card?

[Roving-Ronin]

Might be asking too much, but whilst the full card has the option for PV kWh so far today / possible kWh left in the day, on the left side. Is there anyway to have the option for the top right to have a 'Total Active Power W (as this moment used in the house' / 'Total kWh Used Today'? Space wise might be an option of if your not using/displaying the AUX boxes, then this could be enabled in the unused AUX card space?

[slipx06]

@Roving-Ronin Just some feedback

The Battery 'Optional Sensor' for the (battery) Energy, that allows using a sensor appears to be reading the sensors as Watts only?
If so this is an issue, as in HA there device_class for batteries is 'SensorDeviceClass.ENERGY_STORAGE' and it allows supported units of "Wh, kWh, MWh, MJ, GJ".

This has been fixed. Thanks for raising it

For Essential Load, when using all Essential Load 1 - 4, I note that the name tags of 1-2 are are under the boxes, whilst 3-4 are under them. Wondering if all these names should be on the 'outside' of the boxes (i.e. 1-2 on the top and 3-4 under) that would allow for space inside of the boxes (closest the house icon) for all Essential Loads to have Essential Load Extras?. So would look like this (ignore all daily kWh examples are the same..quick copy / paste):

Its possible but moving things around is a bit of a pain. I'll need to investigate a bit more if it makes sense

If displaying the grid cost it is aligned left of the power line come out of the grid plyon, when also using the non_essential_load2_extra (to display total kWh it used today) this is aligned to be on the outside oof the non_essential_load2 box and extend right. This causes these two items to overlap each other.

Thanks I've fixed the alignment and split the energy_cost_buy and energy_cost_sell over two lines to make more space for the extra info,

Using 4.38 (Full card) and found that if I turn off the AUX being displayed, that he Daily Energy kWh for Essential jumps to the right, see:

I've standardized the placement of the daily load and daily aux. They now appears above the rectangle.

Also wondering, as we already have Essential / AUX / Grid with their Daily kWh counters displayed, would it be possible to have this also for Non-Essential ? Maybe like:

Parked as an idea. Thanks

Looking at the card, updated with different sensors to follow the SunSynk flows, I noticed that the 'Dynamic Colour' functionality doesn't extend to the 'box showing Hz / V / kW' or the 'Non Essential' boxes. Any chance that the dynamic colour function could be extended to there?

Getting this logic correct is going to be challenging and the way non-essential loads are handled can vary depending on settings, wiring and inverter. I dont really want to go down that rabbit hole.

Are 2 and 5 automatically calculated within the card, if the others are provided?

5 - essential_power is the only value that the card will calculate based on supplied sensors i.e. essential = inverter_power_175 + grid_power_169 - aux_power_166

For the Hauwei 4 (grid) is natively a negative for importing, whilst 3 is a positive for consumption, so '2 = -4 - 3' ends up incorrect, so in the custom sensor we have to use '2 = 4 + 3'. Would this cause any issues your aware of in the card?

No that should be fine.

Might be asking too much, but whilst the full card has the option for PV kWh so far today / possible kWh left in the day, on the left side. Is there anyway to have the option for the top right to have a 'Total Active Power W (as this moment used in the house' / 'Total kWh Used Today'? Space wise might be an option of if your not using/displaying the AUX boxes, then this could be enabled in the unused AUX card space?

Can you share mockup of how this will look?

[Roving-Ronin]

@slipx06 I have to get a moment to do the mock up... been busy. It was essentially just the same as the top left side, but on the top right, displaying the Total kWh used for the house (that a user could then map to the House Consumption feed into a utility_meter to show overall usage (i.e. PV + Grid + Battery)) and next to that the House Consumption showing the Active Power / current Watts or kW being used for the house (i.e. Essential + Non-Essential... optional ? AUX)

Anyhow, just wondering if needed would it be possible to have an 'Invert' option for Non-Essential' ?
I have to try some more options, but atm finding that if I invert the grid to make it work, then Non-Essential (and Essential and other places are all out of whack... showing postive W when they should be negative to denote consumption/draw etc.

[slipx06]

Hi Do you have show_absolute option set to true under battery options?

[Roving-Ronin]

Hi, Yes for the site with battery, absolute is ON.

[slipx06]

Then it will only ever show a positive number for battery power. Try turn it off.

[Roving-Ronin]

Well this doesn't help... wlcrs/huawei_solar#720
Individual battery sensor gives one reading, and the new Huawei 'Batteries' sensor that should give the total of all connected batteries (but there is only 1 attached anyhow) is reading something different. :-(

[Roving-Ronin]

Hi @slipx06,

In regards the changing of the line to reflect where the power is coming from. In this example below, shouldn't the small line between the inverter box and the load box be showing as yellow/solar, at least for that small section or (maybe) up to the point it branches off to the non-essential load ?

[Roving-Ronin]

@slipx06
Apologies my GitHub notifications has been hammered and I can't find the original issue/discussion I raised the question if it would be possible to add in support for showing the:
a) Total Power / Load that is being consumed in the house at any moment
b) Total Energy consumed in the house for the day (from all sources)

At the time I suggested that maybe it could be a conditional item, that is available IF the AUX is disabled (and the AUX section of the card then unused). You asked if I could paste a screenshot back as to what/where I was talking about.

As such please find below (apologies on slow reply, just snowed under for a while now). I have highlighted the AUX area I was thinking off with 'Box 1' or broken into two parts in 'Boxes 2 and 3' would be another alternative. Doubt it could fit, but utopian would be across the top of the essential 1 and 2 boxes on the top right of the card [showing 244W / 165W], so it could be a 2.30kW / 34.5kWh with a smaller 'Load / Daily Energy' underneath it) that would be like the 'Daily Solar / Left Today' on the left top of the card.

Active Load / Daily Cons. are other descriptors that could be used to reduce the letter count in those examples also.?

[Roving-Ronin]

If the DAILY LOAD above the 'Essential Load' Power/Watts is used for showing the total consumption of the house for the day (as per above screenshots) then only the current Active Power / Load (Watts / kW) would be needed to be add.