@djaust
Thanks for providing the code so quickly, much appreciated. Works like a charm
@djaust could you share the code that you use for that card?
Sure, it’s using the custom graph card and some vertical and horizontal stack cards.
type: vertical-stack
cards:
- type: horizontal-stack
cards:
- type: custom:mini-graph-card
name: Current Production
unit: kW
decimals: 2
value_factor: -3
entities:
- sensor.envoy_current_energy_production
- type: custom:mini-graph-card
name: Current Consumption
unit: kW
decimals: 2
value_factor: -3
entities:
- sensor.envoy_current_energy_consumption
- type: horizontal-stack
cards:
- type: custom:mini-graph-card
name: Daily Production
unit: kWh
hours_to_show: 120
show:
graph: bar
aggregate_func: max
group_by: date
decimals: 2
value_factor: -3
entities:
- sensor.envoy_today_s_energy_production
- type: custom:mini-graph-card
name: Daily Consumption
unit: kWh
hours_to_show: 120
show:
graph: bar
aggregate_func: max
group_by: date
decimals: 2
value_factor: -3
entities:
- sensor.envoy_today_s_energy_consumption
- type: entity
entity: sensor.inst_energy_difference
Good Morning,
I set up this integration new on a new HA instance (2021-6, now updated to 2021-7-4) for two Envoy’s on the same network.
One is an original Envoy, one is the new Envoy IQ.
Both were manually configured through the Add Integration window (not autodiscovered).
The readings work great, and all the inverters show up.
The issue is the global sensors (energy_production, energy_consumption, etc) do not have unique IDs assigned to them. This leads to fun issues with logging when HA is restarted.
I’ve looked through the new sensor configuration and I can’t figure out why this is happening.
Any assistance would be appreciated.
Thanks,
Peter
hi,
At the current author of this integration, would it be possible to update the classes of the sensors ?
If this is done, we can use the input from enphase in the new energy balance / monitor tab from the latest release. 2021.8 
thank you in advance fot the effort.
The enphase integration was updated as part of beta process. So it will already work with the energy integration. However, there is some additional work required to create the required long term sensors.
1 Like
ah. ok. cool. I indeed was talking about the long term sensors.
I will give it a go and report back.
Thank you for the reply and effort during the beta period
Yeah, it’d be nice to see them rolled in.
But while they’re not, then you can create them yourself if needed.
Im a bit at a loss.
What kind of sensor data is required to be fed to the Configuration > Energy area.
Would that be only (k)Wh data? or W?
By default, I can only see the first, the Wh sensors from my p1 meters production/consumption and solar (enphase lifetime) production. These are sensors of class energy, not power.
The graph I see after 2 hours is still incorrect.
Hopefully you can help me get my head on straight again
uodate
looking at the picture in your linked post more closely, I beginning to think I AM doing things correctly… Hope you can confirm that.
Under solar palels I have selected the Enphase_new_lifetime_energy Production (Wh)
Under Electricyti Grid I have the Energy consumption tarrif 1 and 2 and the same with production (2x Wh)
.
So I think names of sensors created by the envoy integration have been changed slightly from what I used (my integrations been running for almost a year).
So instead of sensor.envoy_current_energy_consumption it is now sensor.envoy_current_power_consumption
And instead of sensor.envoy_current_energy_production it is now sensor.envoy_current_power_production
You need Energy Sensors (i.e. kWh or Wh), not power ones.
So you need to convert the power sensors into an energy sensor using the Reimann Sum integration.
The sensor.envoy_lifetime_energy_production sensor is used for the solar production measures.
1 Like
I am not convinced that this integration necessarily needs to provide all the sensors required for the energy dashboard out of the box. After all, the Envoy device measures your energy consumption and solar production, not the energy you import from the grid or export to the grid.
Using helpers like integration, utility meter or templates may still be required. That’s a bit clunky at the moment, but I’m sure will improve over the next few releases.
1 Like
For any newbies that want their Enphase Envoy to work with the new Energy feature in Home Assistant 2021.8 please see Enhpase Envoy on 2021.8 with new Energy feature
2 Likes
Hello, I have enphase batteries, I would willing to help test.
How did you get the data out of envoy into HA? What config did you use?
yes, used this. thanks mate
Hi averybody, please pelase help me because i m not available to connect my enphase systems to HA.
I m included in the configuation. yaml this informatio:
sensor:
- platform: enphase_envoy
ip_address:.x.x.x.x
monitored_conditions:- production
- daily_production
- consumption
- daily_consumption
I can connect to enphase by web with not problem, but impossible in the HA.
Please let me know if I have any problem.
Is there a reason you are trying to include this integration via the config file instead of via the UI? Configuration via config file has been deprecated, and it should have automatically been converted to a UI configuration entry, and thus any further changes in your config file to this entry have no effect.
Please let us know if you see any error messages related to this integration in your log file.
I m Including it in the configuration.yaml because im new in HA and I didn´t know that this method has been deprecated.
No error in my log.
I introduce in the UI
My Enphase Ip
User : Envoy
And in password two methosd, one in blank and another wiht las 6 digits of me S/N Enphase
Always I have connection error.
And I can access to my enphase directly with envoy.local or ip in the navigator.
Maybe would it be necessary to connect enphase with Cable?
Thanks a lot.
Hi , Anybody has a script to start an action when the diference between consumption and production ara as an example 500 W between each other?
It would be helpful to active maybe the swimming pool, only when we are producing more than we are consumption
Are easier, is there a possibility to the exported grid in our isntallation?
Create the sensors in the first post of this thread. This will give you the import or export values that you can use as a trigger in your automations - If sensor.grid_export_power > 500 do something. It will also track export (and import) amounts
1 Like
Hi,
Yep, I have done exactly that with my pool.
You are on the right track with the ‘difference’. This is how we find out how much grid power is either being imported or exported.
Here is a very simple template sensor that will give you a positive or negative number.
If production is > than consumption, then you will have a positive number to indicate excess power being exported to grid.
- sensor:
- name: Net Power
state_class: measurement
unit_of_measurement: W
device_class: power
icon: mdi:transmission-tower
state: >
{% set production = states('sensor.solar_production') | int %}
{% set consumption = states('sensor.house_consumption') | int %}
{{ (production - consumption) }}
And then here is my automation.
alias: Pool Pump On
description: ''
trigger:
- platform: numeric_state
above: '1100'
for:
hours: 0
minutes: 10
seconds: 0
milliseconds: 0
entity_id: sensor.net_power
condition:
- condition: state
entity_id: switch.sonoff
state: 'off'
action:
- scene: scene.pool_pump_on
- service: notify.notify
data_template:
message: Pool Pump on {{ states('sensor.net_power') }} Watts
If you want a seperate sensor for grid import and grid export, then I suggest reading the post here
1 Like