Alright, here is a simple configuration (Home Assistant 0.87.0.dev0, power-wheel-card from dev branch from today):
I assume that your Envoy-S is already set up and working:
- platform: enphase_envoy
ip_address: <Envoy-S IP Address>
Next, you will need to create 2 additional template sensors to calculate the currently exported/imported electricity:
- platform: template
sensors:
exporting:
friendly_name: "Current Energy Exporting"
value_template: "{{ [0, (states('sensor.envoy_current_energy_production') | int - states('sensor.envoy_current_energy_consumption') | int)] | max }}"
unit_of_measurement: 'W'
icon_template: 'mdi:flash'
importing:
friendly_name: "Current Energy Importing"
value_template: "{{ [0, (states('sensor.envoy_current_energy_consumption') | int - states('sensor.envoy_current_energy_production') | int)] | max }}"
unit_of_measurement: 'W'
icon_template: 'mdi:flash'
And then the Lovelace configuration (using the editor in the UI) looks like this:
grid_power_consumption_entity: sensor.importing
grid_power_production_entity: sensor.exporting
solar_power_entity: sensor.envoy_current_energy_production
title_power: Power distribution
type: 'custom:power-wheel-card'
Et voilĂ , this is how all that looks like:
I see - I havenât been part of that journey myself, but I agree that the cost view may be a bit too much, and it wouldnât work for me anyway because I pay more when buying electricity than I am being reimbursed when selling electricity.
I guess the question would be if it is more desirable to have a generic card that works with many inverters, smart metres, etc. and thus likely requires to add some template sensors to calculate intermediate values, or instead have a card just for a single platform such as the Envoy-S that calculates all the required values under the hood.