Flow Sensors

[AviadorLP]

I'm now trying to write templates for sensors that show actual power transfers from one sensor to the other, like

sensor.grid2battery
sensor.grid2house
sensor.solar2battery
sensor.solar2house

will be very useful for some more complex power charts that need this, like the custom tesla power chart.
Just trying to get my head around the math involved in this, in every case scenario.
when i finish i will post here.
Maybe you'll find it useful.

[AviadorLP]

With the help of wills106 i started using this flow chart:

[AviadorLP]

But i wrote several templates from wills106 SolaX integration sensors, like i said and now i'm using this Moving Flow Chart:

But still debugging the templates.
The math is complicated because for this to work all power input sensors + power output sensors must add up to 0. So i had to correct the House Load to account for the inverter own power consumption and power losses due to power conversions and round ups and not accurate sensor readings.

Will drop the code here after i think its fully debugged, and i check that all is correct in different scenarios and different SolaX Charger Use Modes.

[AviadorLP]

Ok just finished creating the template and debugging, here is the code with the new flow sensors derived from wills106 integration. The new sensors that can be used for actual power flow charts (APF) are:

SolaX APF Inverter Power Consumption
SolaX APF Real House Load .... witch includes the inverter power consumption and corrections
SolaX APF Grid2House
SolaX APF Grid2Batt
SolaX APF Batt2House
SolaX APF Batt2Grid
SolaX APF Solar2Grid
SolaX APF Solar2House
SolaX APF Solar2Batt

Now you can create or just watch the actual flow of the power flow inside your home at each given time.
I do not know if this will work on non battery users....

# Templates for SolaX Actual Powerflow transfer charts (APF - Actual PowerFlow)
# Requires Wills106 modbus SolaX Integration
#
# For the math to add up a new Real House Load must be calculated and used, witch includes
# the inverter consumption and excludes rounding errors and corrects inaccurate power readings.
#
# It never made sense that inbound power sometimes does not equal outbound power. This fixes it!
#
# Developed by AviadorLP

template:
#   Inverter consumption and power losses due to Inverter transfers and power conversions (AC/DC)
#   excludes rounding errors made worst by the fact that solax rounds all sensors readings to INT
#   Ocasionally this might be negative probably due to cumulative errors in not so accurate power readings.
  - name: SolaX APF Inverter Power Consumption
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: "{{ states('sensor.solax_pv_total_power')|int(default=0) - states('sensor.solax_battery_power_charge')|int(default=0) - states('sensor.solax_inverter_power')|int(default=0) }}"

# Real House Load Includes Inverter consumption and transfer conversions and losses and rounding errors.
# It never made sense that inbound sometimes power does not equal outbound power. This fixes it!
  - name: SolaX APF Real House Load
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: "{{ states('sensor.solax_house_load')|int(default=0) + states('sensor.solax_apf_inverter_power_consumption')|int(default=0) }}"
    icon: mdi:home-lightning-bolt

  - name: SolaX APF Grid2House
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state:  >
      {% if states('sensor.solax_grid_import')|int(default=0) > states('sensor.solax_apf_real_house_load')|int(default=0) %}
        {{ states('sensor.solax_apf_real_house_load')|int(default=0) }}
      {% else %}
        {{ states('sensor.solax_grid_import')|int(default=0) }}
      {% endif %}

  - name: SolaX APF Grid2Batt
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_grid_import')|int(default=0) > states('sensor.solax_apf_real_house_load')|int(default=0) %}
        {{ states('sensor.solax_grid_import')|int(default=0) - states('sensor.solax_apf_real_house_load')|int(default=0) }}
      {% else %}
        0
      {% endif %}

  - name: SolaX APF Batt2House
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_battery_power_charge')|int(default=0) < 0 %}
        {% if states('sensor.solax_battery_power_charge')|int(default=0)|abs > states('sensor.solax_apf_real_house_load')|int(default=0) %}
          {{ states('sensor.solax_apf_real_house_load')|int(default=0) }}
        {% else %}
          {{ states('sensor.solax_battery_power_charge')|int(default=0)|abs }}
        {% endif %}
      {% else %}
        0
      {% endif %}

# This might be called house to grid, and can happen in rare circunstances,
# like when the inverter is not able to do a precise adjustment of power fast enough
# or when you want to force a discharge of the battery or something...
# But it only happens with battery or other power generator users.
  - name: SolaX APF Batt2Grid
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_battery_power_charge')|int(default=0) < 0 %}
        {% if states('sensor.solax_battery_power_charge')|int(default=0)|abs > states('sensor.solax_apf_real_house_load')|int(default=0) %}
          {{ states('sensor.solax_battery_power_charge')|int(default=0)|abs - states('sensor.solax_apf_real_house_load')|int(default=0) }}
        {% else %}
          0
        {% endif %}
      {% else %}
        0
      {% endif %}

  - name: SolaX APF Solar2Grid
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_grid_export')|int(default=0) > states('sensor.solax_apf_batt2grid')|int(default=0) %}
        {{ states('sensor.solax_grid_export')|int(default=0) - states('sensor.solax_apf_batt2grid')|int(default=0) }}
      {% else %}
        0
      {% endif %}

  - name: SolaX APF Solar2House
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_pv_total_power')|int(default=0) > 0 and states('sensor.solax_apf_real_house_load')|int(default=0) > states('sensor.solax_apf_batt2house')|int(default=0) + states('sensor.solax_grid_import')|int(default=0) %}
        {% if states('sensor.solax_pv_total_power')|int(default=0) > states('sensor.solax_apf_real_house_load')|int(default=0) - states('sensor.solax_apf_batt2house')|int(default=0) - states('sensor.solax_apf_grid2house')|int(default=0) %}
          {{ states('sensor.solax_apf_real_house_load')|int(default=0) - states('sensor.solax_apf_batt2house')|int(default=0) - states('sensor.solax_apf_grid2house')|int(default=0) }}
        {% else %}
          {{ states('sensor.solax_pv_total_power')|int(default=0) }}
        {% endif %}
      {% else %}
        0
      {% endif %}

  - name: SolaX APF Solar2Batt
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_pv_total_power')|int(default=0) > 0 and states('sensor.solax_battery_power_charge')|int(default=0) > 0 %}
        {% if states('sensor.solax_battery_power_charge')|int(default=0) > states('sensor.solax_apf_grid2batt')|int(default=0) %}
          {% if states('sensor.solax_pv_total_power')|int(default=0) - states('sensor.solax_apf_solar2house')|int(default=0) > states('sensor.solax_battery_power_charge')|int(default=0) - states('sensor.solax_apf_grid2batt')|int(default=0) %}
            {{ states('sensor.solax_battery_power_charge')|int(default=0) - states('sensor.solax_apf_grid2batt')|int(default=0) }}
          {% else %}
            {{ states('sensor.solax_pv_total_power')|int(default=0) - states('sensor.solax_apf_solar2house')|int(default=0) - states('sensor.solax_apf_solar2grid')|int(default=0) }}
          {% endif %}
        {% else %}
          0
        {% endif %}
      {% else %}
        0
      {% endif %}

[AviadorLP]

For those users who just want to have that amazing actual moving power flow chart in the picture above working,
here is the easy way to do it:

I really dont know if this will work for non battery users...

First install from HACS frontend the -> Tesla style solar power card
I only allows 2 appliances for now so i created a template also that replaces one appliance for the one that is presently consuming the most power.
The second one i recommend you use your car charger entity or your favorite power entity.
next copy the code below to a new yaml file and insert it in your packages folder,
and replace the sensors and short names for the sensors that make sense to you in the beginning of the code.

# Templates for SolaX Actual Powerflow transfer charts (APF - Actual PowerFlow)
# Requires wills106 modbus SolaX Integration, my great thanks to wills106 for his great work.
#
# For the math to add up a new Real House Load must be calculated and used, witch includes
# the inverter consumption and excludes rounding errors and corrects inaccurate power readings.
#
# It never made sense that inbound power sometimes does not equal outbound power. This fixes it!
#
# Developed by AviadorLP

sensor:
  - platform: time_date
    display_options:
      - 'time'
  - platform: min_max
    name: Highest Power Appliance
    type: max 
    entity_ids:
      - sensor.shelly_lights_power
      - sensor.recirculacao_de_agua_power
      - sensor.maquina_de_lavar_roupa_power
      - sensor.maquina_de_secar_roupa_power
      - sensor.termoacumulador_power
# replace with what you need at least 2 entities required and also 
# in Highest Power Appliance Short Name if you want or "Highest" will be shown

template:
- sensor:
  - name: Highest Power Appliance Short Name
    state: >
      {% if is_state_attr('sensor.highest_power_appliance', 'max_entity_id', 'sensor.shelly_lights_power') %}
        Lights
      {% elif is_state_attr('sensor.highest_power_appliance', 'max_entity_id', 'sensor.recirculacao_de_agua_power') %}
        Water
      {% elif is_state_attr('sensor.highest_power_appliance', 'max_entity_id', 'sensor.maquina_de_lavar_roupa_power') %}
        Washing
      {% elif is_state_attr('sensor.highest_power_appliance', 'max_entity_id', 'sensor.maquina_de_secar_roupa_power') %}
        Drying
      {% elif is_state_attr('sensor.highest_power_appliance', 'max_entity_id', 'sensor.termoacumulador_power') %}
        Termo
      {% else %}
        Highest
      {% endif %}

  - name: SolaX APF Mode Short
    state: >
      {% if is_state('sensor.solax_run_mode', 'Normal Mode') %}
        {% if is_state('sensor.solax_charger_use_mode', 'Force Time Use') %}
          {% if states('sensor.solax_charger_start_time_1') <= states('sensor.time') <= states('sensor.solax_charger_end_time_1') %}
            {% if is_state('sensor.solax_allow_grid_charge', 'Period 1 Allowed') or is_state('sensor.solax_allow_grid_charge', 'Both Allowed') %}
              Charge
            {% else %}
              Sol2Bat
            {% endif %}
          {% elif states('sensor.solax_charger_start_time_2') <= states('sensor.time') <= states('sensor.solax_charger_end_time_2') %}
            {% if is_state('sensor.solax_allow_grid_charge', 'Period 2 Allowed') or is_state('sensor.solax_allow_grid_charge', 'Both Allowed') %}
              Charge
            {% else %}
              Sol2Bat
            {% endif %}
          {% else %}
            Normal
          {% endif %}
        {% elif is_state('sensor.solax_charger_use_mode', 'Back Up Mode') %}
          {% if states('sensor.solax_backup_charge_start') <= states('sensor.time') <= states('sensor.solax_backup_charge_end') %}
            {% if is_state('sensor.solax_allow_grid_charge', 'Enabled') %}
              Charge
            {% else %}
              BackUp
            {% endif %}
          {% else %}
            Normal
          {% endif %}
        {% else %}
          Normal
        {% endif %}
      {% elif is_state('sensor.solax_run_mode', 'Off Mode') %}
        Off
      {% elif is_state('sensor.solax_run_mode', 'Permanent Fault Mode') %}
        Fault
      {% elif is_state('sensor.solax_run_mode', 'Update Mode') %}
        Update
      {% elif is_state('sensor.solax_run_mode', 'EPS Check Mode') %}
        EPS-X
      {% elif is_state('sensor.solax_run_mode', 'EPS Mode') %}
        EPS
      {% elif is_state('sensor.solax_run_mode', 'Off-Grid Waiting') %}
        OG Wait
      {% elif is_state('sensor.solax_run_mode', 'Self Test') %}
        Test
      {% elif is_state('sensor.solax_run_mode', 'Idle Mode') %}
        Idle
      {% else %}
        {{ states('sensor.solax_run_mode') }}
      {% endif %}

#   Inverter consumption and power losses due to Inverter transfers and power conversions (AC/DC)
#   excludes rounding errors made worst by the fact that solax rounds all sensors readings to INT
#   Ocasionally this might be negative probably due to cumulative errors in not so accurate power readings.
  - name: SolaX APF Inverter Power Consumption
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: "{{ states('sensor.solax_pv_total_power')|int(default=0) - states('sensor.solax_battery_power_charge')|int(default=0) - states('sensor.solax_inverter_power')|int(default=0) }}"

# Real House Load Includes Inverter consumption and transfer conversions and losses and rounding errors.
# It never made sense that inbound sometimes power does not equal outbound power. This fixes it!
  - name: SolaX APF Real House Load
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: "{{ states('sensor.solax_house_load')|int(default=0) + states('sensor.solax_apf_inverter_power_consumption')|int(default=0) }}"
    icon: mdi:home-lightning-bolt

  - name: SolaX APF Grid2House
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state:  >
      {% if states('sensor.solax_grid_import')|int(default=0) > states('sensor.solax_apf_real_house_load')|int(default=0) %}
        {{ states('sensor.solax_apf_real_house_load')|int(default=0) }}
      {% else %}
        {{ states('sensor.solax_grid_import')|int(default=0) }}
      {% endif %}

  - name: SolaX APF Grid2Batt
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_grid_import')|int(default=0) > states('sensor.solax_apf_real_house_load')|int(default=0) %}
        {{ states('sensor.solax_grid_import')|int(default=0) - states('sensor.solax_apf_real_house_load')|int(default=0) }}
      {% else %}
        0
      {% endif %}

  - name: SolaX APF Batt2House
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_battery_power_charge')|int(default=0) < 0 %}
        {% if states('sensor.solax_battery_power_charge')|int(default=0)|abs > states('sensor.solax_apf_real_house_load')|int(default=0) %}
          {{ states('sensor.solax_apf_real_house_load')|int(default=0) }}
        {% else %}
          {{ states('sensor.solax_battery_power_charge')|int(default=0)|abs }}
        {% endif %}
      {% else %}
        0
      {% endif %}

# This might be called house to grid, and can happen in rare circunstances,
# like when the inverter is not able to do a precise adjustment of power fast enough
# or when you want to force a discharge of the battery or something...
# But it only happens with battery or other power generator users.
  - name: SolaX APF Batt2Grid
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_battery_power_charge')|int(default=0) < 0 %}
        {% if states('sensor.solax_battery_power_charge')|int(default=0)|abs > states('sensor.solax_apf_real_house_load')|int(default=0) %}
          {{ states('sensor.solax_battery_power_charge')|int(default=0)|abs - states('sensor.solax_apf_real_house_load')|int(default=0) }}
        {% else %}
          0
        {% endif %}
      {% else %}
        0
      {% endif %}

  - name: SolaX APF Solar2Grid
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_grid_export')|int(default=0) > states('sensor.solax_apf_batt2grid')|int(default=0) %}
        {{ states('sensor.solax_grid_export')|int(default=0) - states('sensor.solax_apf_batt2grid')|int(default=0) }}
      {% else %}
        0
      {% endif %}

  - name: SolaX APF Solar2House
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_pv_total_power')|int(default=0) > 0 and states('sensor.solax_apf_real_house_load')|int(default=0) > states('sensor.solax_apf_batt2house')|int(default=0) + states('sensor.solax_grid_import')|int(default=0) %}
        {% if states('sensor.solax_pv_total_power')|int(default=0) > states('sensor.solax_apf_real_house_load')|int(default=0) - states('sensor.solax_apf_batt2house')|int(default=0) - states('sensor.solax_apf_grid2house')|int(default=0) %}
          {{ states('sensor.solax_apf_real_house_load')|int(default=0) - states('sensor.solax_apf_batt2house')|int(default=0) - states('sensor.solax_apf_grid2house')|int(default=0) }}
        {% else %}
          {{ states('sensor.solax_pv_total_power')|int(default=0) }}
        {% endif %}
      {% else %}
        0
      {% endif %}

  - name: SolaX APF Solar2Batt
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    state: >
      {% if states('sensor.solax_pv_total_power')|int(default=0) > 0 and states('sensor.solax_battery_power_charge')|int(default=0) > 0 %}
        {% if states('sensor.solax_battery_power_charge')|int(default=0) > states('sensor.solax_apf_grid2batt')|int(default=0) %}
          {% if states('sensor.solax_pv_total_power')|int(default=0) - states('sensor.solax_apf_solar2house')|int(default=0) > states('sensor.solax_battery_power_charge')|int(default=0) - states('sensor.solax_apf_grid2batt')|int(default=0) %}
            {{ states('sensor.solax_battery_power_charge')|int(default=0) - states('sensor.solax_apf_grid2batt')|int(default=0) }}
          {% else %}
            {{ states('sensor.solax_pv_total_power')|int(default=0) - states('sensor.solax_apf_solar2house')|int(default=0) - states('sensor.solax_apf_solar2grid')|int(default=0) }}
          {% endif %}
        {% else %}
          0
        {% endif %}
      {% else %}
        0
      {% endif %}

Then restart HASS and create new custom card with the following code:
Change what you need first because after you save comments will disappear....

type: custom:tesla-style-solar-power-card
name: SolaX Actual Power Flow
show_w_not_kw: 1
hide_inactive_lines: 1
grid_to_house_entity: sensor.solax_apf_grid2house
grid_to_battery_entity: sensor.solax_apf_grid2batt
generation_to_grid_entity: sensor.solax_apf_solar2grid
generation_to_battery_entity: sensor.solax_apf_solar2batt
generation_to_house_entity: sensor.solax_apf_solar2house
battery_to_house_entity: sensor.solax_apf_batt2house
battery_to_grid_entity: sensor.solax_apf_batt2grid
grid_entity: sensor.solax_measured_power
# grid_extra_entity: sensor.daikin_outside_temperature  ----> Change to whatever extra info you want to see
house_entity: sensor.solax_apf_real_house_load
house_extra_entity: sensor.solax_apf_inverter_power_consumption
generation_entity: sensor.solax_pv_total_power
generation_extra_entity: sensor.solax_apf_mode_short
battery_entity: sensor.solax_battery_power_charge
battery_extra_entity: sensor.solax_battery_capacity
appliance1_consumption_entity: sensor.highest_power_appliance
appliance1_extra_entity: sensor.highest_power_appliance_short_name
appliance1_icon: mdi:flash
# appliance2_consumption_entity: sensor.escritorio_computers_power  ----> Change to your favorite device
# appliance2_extra_entity: sensor.ups_capacity_status               ----> Change to your favorite info
# appliance2_icon: mdi:desktop-tower-monitor                        ----> Change to your favorite icon

Click save, done, exit the lovelace editor mode (it wont update well when on)
Refresh your browser once or twice and then enjoy !

[richsimpson]

Great work, just what I was looking for.

[richsimpson]

I do have a question though...

My setup currently doesn't see the charge rate on my EV. Dumb Rolec which I have added some smartness to, I can detect if it is charging based on a switch and some assumptions over the energy usage through my home.

I do have 3 other energy hogs running through smart plugs. Dishwasher, Washing Machine and Tumble Dryer. I have them set as the Highest Use items but of course what happens when they are all complete is the item with the highest standby usage (1w perhaps) is still the highest of the three.

Is there some way to turn off the highest use item from the display, when the usage is below say 50w? Returning to a standard 4 blob of solar/grid/home and battery?
Perfect here when in use:

Not so clever when not in use:

Also to disable the inverter use/calculation item from showing, is that possible. Happy to see in the first picture the home is consuming 2547w total, not so interested that the 87w is actually displayed.
Just removing the line house_extra_entity: sensor.solax_apf_inverter_power_consumption does seem to work, it isn't causing issues elsewhere though is it?

Great work though. Thanks in advance if you can help on these questions.

[richsimpson]

Later the highest use becomes disjoined to the map and shows a 0w item

[AviadorLP]

I do have a question though...

My setup currently doesn't see the charge rate on my EV. Dumb Rolec which I have added some smartness to, I can detect if it is charging based on a switch and some assumptions over the energy usage through my home.

I do have 3 other energy hogs running through smart plugs. Dishwasher, Washing Machine and Tumble Dryer. I have them set as the Highest Use items but of course what happens when they are all complete is the item with the highest standby usage (1w perhaps) is still the highest of the three.

Is there some way to turn off the highest use item from the display, when the usage is below say 50w? Returning to a standard 4 blob of solar/grid/home and battery? Perfect here when in use:

Not so clever when not in use:

Well i don't think in this case you can enable or disable a bubble based on a condition,
but i could adapt so below a given threshold of your choice it will show 0 W or maybe nothing and the title 'None' or 'Highest' or simply no title at all.... ???

Also to disable the inverter use/calculation item from showing, is that possible. Happy to see in the first picture the home is consuming 2547w total, not so interested that the 87w is actually displayed. Just removing the line house_extra_entity: sensor.solax_apf_inverter_power_consumption does seem to work, it isn't causing issues elsewhere though is it?

Great work though. Thanks in advance if you can help on these questions.

No, no issues at all just delete it or replace with some entity more useful for you. i personally like to see the outside temperature over the grid bubble and the inside temperature over the house bubble.

[richsimpson]

Whilst the code in this thread and creating a package works well, the graphics on the tesla powerwall app are a bit meh...
I like the option to add specific devices, and also the option to remove the flow lines when they are not active.

It doesn't seem to render as nicely though and harder to read, The values are too big but also not bold enough.

I have gone back to the powerflow card in HACS. Looks more like the energy dash plus easier to read on a phone screen. Aging eyes !

To get the live data this was my manual lovelace card

type: custom:power-flow-card
title: Live Data
entities:
battery: sensor.solax_battery_power_charge
battery_charge: sensor.solax_battery_capacity
grid:
consumption: sensor.solax_grid_import
production: sensor.solax_grid_export
solar: sensor.solax_pv_total_power
inverted_entities: battery
watt_threshold: 1000
min_flow_rate: 1
max_flow_rate: 5

Might be helpful to someone, might not! Still really appreciate the efforts to put that package together though

[tomcoleman]

struggling to get this working but looks like excatly what i need - happy to buy a beer for help.

[richsimpson]

What are you trying and how far have you got. Happy to support.

[tomcoleman]

What are you trying and how far have you got. Happy to support.

for example it is showing my solar production and house load as the same value

my code is as follows on my lovelace-ui.yaml

'''
#################################################
# #
# SOLAR #
# #
#################################################
- type: grid
title: Solar & Power
view_layout:
grid-area: solar
columns: 1
cards:

      - type: 'custom:tesla-style-solar-power-card'


        generation_icon: 'mdi:solar-power'
        house_without_appliances_values: 1
        show_w_not_kw: 1
        show_gap: true

###Grid Power###
grid_to_house_entity: sensor.solax_apf_grid2house
grid_to_battery_entity: sensor.solax_apf_grid2batt
###Solar Power###
generation_to_grid_entity: sensor.solax_apf_solar2grid
generation_to_battery_entity: sensor.solax_apf_solar2batt
generation_to_house_entity: sensor.solax_apf_solar2house

###Battery Power###
battery_to_house_entity: sensor.solax_apf_batt2house
battery_to_grid_entity: sensor.solax_apf_batt2grid
grid_entity: sensor.solax_measured_power
house_entity: sensor.solax_apf_real_house_load
house_extra_entity: sensor.solax_apf_inverter_power_consumption
generation_entity: sensor.solax_pv_total_power_2
generation_extra_entity: sensor.solax_apf_mode_short
battery_entity: sensor.solax_battery_power_charge
battery_extra_entity: sensor.solax_battery_capacity

        # extra values to show as text above icons
        #battery_extra_entity: sensor.solax_x1h_batpower
        #house_extra_entity: sensor.kitchen_thermostat_current_temperature
        #generation_extra_entity: sensor.openweathermap_cloud_coverage
        #grid_extra_entity: sensor.smart_meter_electricity_import_today
        
        # optional appliances with consumption and extra values
        appliance1_consumption_entity: sensor.psl_247045_current_energy_2
        appliance1_extra_entity: sensor.i3_120_charging_status 
        #appliance2_consumption_entity: sensor.heating_consumption
        #appliance2_extra_entity: sensor.heating_operation
        
        # optional 4 main bubble icons for clickable entities
        #grid_entity: sensor.smart_meter_electricity_import
        #house_entity: sensor.solax_house_load
        #generation_entity: sensor.solax_inverter_power
        #battery_entity: sensor.solax_x1h_batpower

'''

[richsimpson]

ok, i had it working but removed as preferred the other card. You are doing the tesla powerflow card yes?

I sent myself the dashboard info before i removed it but it was like this:

type: custom:tesla-style-solar-power-card

show_w_not_kw: 1

hide_inactive_lines: 1

grid_to_house_entity: sensor.solax_apf_grid2house

grid_to_battery_entity: sensor.solax_apf_grid2batt

generation_to_grid_entity: sensor.solax_apf_solar2grid

generation_to_battery_entity: sensor.solax_apf_solar2batt

generation_to_house_entity: sensor.solax_apf_solar2house

battery_to_house_entity: sensor.solax_apf_batt2house

battery_to_grid_entity: sensor.solax_apf_batt2grid

grid_entity: sensor.solax_measured_power

house_entity: sensor.solax_apf_real_house_load

generation_entity: sensor.solax_pv_total_power

generation_extra_entity: sensor.solax_apf_mode_short

battery_entity: sensor.solax_battery_power_charge

battery_extra_entity: sensor.solax_battery_capacity

show_gap: true

generation_icon: mdi:solar-power-variant

appliance1_consumption_entity: sensor.highest_power_appliance

appliance1_extra_entity: sensor.highest_power_appliance_short_name

appliance1_icon: mdi:flash

You will have to repair the indentations as it didn't save it for me when i emailed it to myself. That was working fine. I just wasn't keen on the graphics

[AviadorLP]

Sorry i have been very busy an now on vacation. I will look at this thread next week to see if i can help out...

[tomcoleman]

" You are doing the tesla powerflow card yes?" - yes i'am! :)

it all seems to be working now (i think) just need to double check the values to make sure the math is 100%

One question is on the battery is there a sensor which shows you what kWh is stored inside the battery as at the moment it only shows what % the battery is, would be nice to see actual kWh value?!

[wills106]

One question is on the battery is there a sensor which shows you what kWh is stored inside the battery as at the moment it only shows what % the battery is, would be nice to see actual kWh value?!

Not to my knowledge, I haven't found one yet and I doubt there will be as it doesn't report that in the Cloud Portal.
You would have to manually build that with a Template Sensor.

[tomcoleman]

One question is on the battery is there a sensor which shows you what kWh is stored inside the battery as at the moment it only shows what % the battery is, would be nice to see actual kWh value?!

Not to my knowledge, I haven't found one yet and I doubt there will be as it doesn't report that in the Cloud Portal. You would have to manually build that with a Template Sensor.

will thanks for your reply - really helpful and fully supportive of your work - think i sent you a beer :)

on the template sensor would there need to be some math to work that out then or is it better to leave it / too complex for my monkey tiny brain

[wills106]

on the template sensor would there need to be some math to work that out then or is it better to leave it

Personally I am not sure what benefit it would give you. As I don't know exactly how you would calculate it.

My Batteries are the 4.5kWh versions.

But is that 4.5kWh from 0-100% or from 10-100%? As you can't set the limit below 10% for the SOC %
Also you would need to dynamically calculate it based on what you set your minimum SOC to. For example 20-100%. As there will be little point to it say you have X amount of kWh left when you drop to 20% as you have bared yourself from using that last 10% available.

[tomcoleman]

mine is the 5.8kw set at 10% limit.

if its easy (enough) todo that would be cool and would send you some £ but if too much ballache then i'll jump out the window and forget about it 👍

[wills106]

  - platform: template
    sensors:
      battery_kwh:
        friendly_name: 'Battery kWh'
        device_class: energy
        unit_of_measurement: "kWh"
        value_template: >-
         {% set battery_kwh = states.sensor.solax_battery_capacity.state %}
         {% if battery_kwh | float<=10 %}0
         {% elif 11 < (battery_kwh|float) <=15 %}0.32
         {% elif 16 < (battery_kwh|float) <=20 %}0.64
         {% elif 21 < (battery_kwh|float) <=25 %}0.96
         {% elif 26 < (battery_kwh|float) <=30 %}1.28
         {% elif 31 < (battery_kwh|float) <=35 %}1.6
         {% elif 36 < (battery_kwh|float) <=40 %}1.92
         {% elif 41 < (battery_kwh|float) <=45 %}2.24
         {% elif 46 < (battery_kwh|float) <=50 %}2.56
         {% elif 51 < (battery_kwh|float) <=55 %}2.88
         {% elif 56 < (battery_kwh|float) <=60 %}3.2
         {% elif 61 < (battery_kwh|float) <=65 %}3.52
         {% elif 66 < (battery_kwh|float) <=70 %}3.84
         {% elif 71 < (battery_kwh|float) <=75 %}4.16
         {% elif 76 < (battery_kwh|float) <=80 %}4.48
         {% elif 81 < (battery_kwh|float) <=85 %}4.8
         {% elif 86 < (battery_kwh|float) <=90 %}5.12
         {% elif 91 < (battery_kwh|float) <=95 %}5.44
         {% elif 96 < (battery_kwh|float) <=100 %}5.8
         {%- endif %}

That with a 5% resolution on the battery. It's also assuming the 5.8kWh is form 10% - 100% and you only have a single battery.
If you have two, then multiply each value after the elif by two, or three etc.

[AviadorLP]

Same thing with a 1% resolution i think...

  - platform: template
    sensors:
      battery_kwh:
        friendly_name: 'Battery kWh'
        device_class: energy
        unit_of_measurement: "kWh"
        value_template: >-
         {% set battery_kwh = states.sensor.solax_battery_capacity.state %}
         {% if battery_kwh|float <= 10 %} 0.00
         {% elif battery_kwh|float >= 100 %} 5.80
         {% elif %} ((battery_kwh|float - 10)*5.80/90)|float|round(2) 
         {%- endif %}

[tomcoleman]

thanks let me give it a whirl now 👍

anyone worked out how to move the bubbles to different posistions or sort the scaling out...

On my wall tablet its off the page for battery icon and text is sometimes cutoff

https://user-images.githubusercontent.com/1098848/179342578-3ff6436c-36f2-4929-b3e7-fe19d6b47c72.png

[richsimpson]

Interested in this. The scaling is what put me off that card. Was ok on PC but looked rubbish on the phone and tablet.

What I do like is the option to only see lines that are in use - so at night the solar to house is removed just showing battery and/or grid.

[tomcoleman]

Interested in this. The scaling is what put me off that card. Was ok on PC but looked rubbish on the phone and tablet.

What I do like is the option to only see lines that are in use - so at night the solar to house is removed just showing battery and/or grid.

i think you can set the value

hide_inactive_lines: 1

which only shows lines in use

scaling is the golden question! as on my tablet it is off the main screen/text wonky.

[tomcoleman]

this is my current view as of now

anyone know why the house is in kWh and not watts?

[richsimpson]

show_w_not_kw: 1

in the dashboard card should do something. Or remove it, or perhaps make it a 0?

[richsimpson]

Actually scrap that, just read the post properly. Looks like a sensor has the wrong calc

[tomcoleman]

Think you set a cutoff limit to move from Watts to KW.

but i have set in my config

show_w_not_kw: 1

so should apply to all values?

[richsimpson]

Yes you are right. I just re-added it and I get it as W for all or KW for all.
Did you add the templates/package from the original post?
Double check none are showing as KW instead of W as the unit of measurement perhaps?

[tomcoleman]

are showing as KW instead of W as the unit of measurement perhaps

i presume it uses the code below which measurment is set in watts

[tomcoleman]

any when i click on the kwh (house icon) opens up and shows as watts

[tomcoleman]

just checked lovelace-ui.yaml and sensor is correct also

but on screen UI displays as kwh!?

[tomcoleman]

or create a new template sensor for your car in W

im not a programmer and only very basic yaml

[AviadorLP]

me neither, i'm an airline pilot :)

[AviadorLP]

Here is a template for you.....
But i can predict a problem your sensor is an energy sensor probably and what is normal for energy
is that they usually are spent energy in time, not power readings....
(example does it show how much you car charged in the last hour or day or something....)
if that is true this does not apply.........
and you should not even use it in the flow chart.
you should try to find a sensor that says power not energy
but since it says current energy maybe its a power reading...

template:
- sensor:
  - name: Car Charger
    device_class: power
    state_class: measurement
    unit_of_measurement: W
    icon: mdi:car-sports
    state: "{{ (states('sensor.psl_247045_current_energy_2')|float(default=0)|round(3)*1000)|int(default=0) }}"

insert this in the end of your configuration.yaml
check for errors in HA and if none restart HA

then just use
appliance1_consumption_entity: sensor.car_charger
remember it still might contain bugs, i do this by trial and error, like i said not a programmer.

[AviadorLP]

also dont use the same sensor for 2 appliances it might confuse the flow chart math

[tomcoleman]

thanks - :)

i'll see what the dev says also.

i just ptu 2 x sensor in there as placeholder untill new car arrives

[tomcoleman]

i tell you what drives me nuts is the scaling / text out of circles

anyone found where in the .js file you need to edit?!

[AviadorLP]

Not an easy task. and i think you cant fix that in the .js file inside you HA.
you need to change the source code in reptilex integration that you can check in his webpage
i think you need java and c and graphic knowledge and i personally don't have it and i'm not interested to learn it.

[tomcoleman]

reptilex integration

i was under the impression everything is from the .js file as if you do a manual install thats the only file that gets copied over to HA?

inside the .js file around lines 5-150 there is allot of mention of lines, pixels, font sizes and SVG's so maybe we could edit something

[AviadorLP]

even if it was that is java script. i learned a little yaml just for ha.
which is relatively easy if you learned some other programing languages before.
but i don't believe you can fix that there.

[AviadorLP]

i think you need to change something here and ask reptilex to prepare it

https://github.com/reptilex/tesla-style-solar-power-card/blob/master/src/TeslaStyleSolarPowerCard.ts

[tomcoleman]

maybe

    `}static get styles(){return r`
    #tesla-style-solar-power-card{
      margin:auto;
      display:table;
      padding: 10px;
      position: relative;
    }
    .acc_container {
        height: 40px;
        width: 40px;
        border: 1px solid black;
        border-radius: 100px;
        padding: 22px;
        color: var(--primary-text-color);
        border-color: var(--primary-text-color);
        position:relative;
        cursor:pointer;
    }

[AviadorLP]

i think you need to change something here and ask reptilex to prepare it

https://github.com/reptilex/tesla-style-solar-power-card/blob/master/src/TeslaStyleSolarPowerCard.ts

this is one of the files in the source code.
But like i said i forgot java and c++ a long time ago and never programmed graphics especially dealing with adjustments to pixel density and i don't even know how to make a complete integration for HA.
Just know how to program simple yaml. And i am ok with easy math (when its not complex math).
Also good at debuging my code when i find something that does not work as expected i usually fix it easily.

[tomcoleman]

i think you need to change something here and ask reptilex to prepare it

https://github.com/reptilex/tesla-style-solar-power-card/blob/master/src/TeslaStyleSolarPowerCard.ts

this is one of the files in the source code. But like i said i forgot java and c++ a long time ago and never programmed graphics especially dealing with adjustments to pixel density and i don't even know how to make a complete integration for HA. Just know how to program simple yaml. And i am ok with easy math (when its not complex math). Also good at debuging my code when i find something that does not work as expected i usually fix it easily.

code looks identicial to the js file, those c files arent even in HA so not sure if it would even call them. I think everything is worked out of the JS file?!

[AviadorLP]

more than 25 years ago i learned basic, pascal, assembly 86, c, c++, java, sql, modula 2 during my studies in a portuguese university. But stopped since then, so it was very easy to learn the basics of yaml.
But what you are needing would require a lot more study that i am willing to do.
Only reptilex or someone on his site can help you there....

[AviadorLP]

I do not have a big problem with scaling because i mostly use google chrome in the pc for ha.
On the app on my phone its a bit wonky but not as much as yours.
try using it from chrome on your tablet maybe its better ?

[ram1t]

Does anyone have the code to get this working with the Solis API?

[AviadorLP]

Hi, use and and adapt this,
it works for any inverter

reptilex/tesla-style-solar-power-card#96 (comment)