Subject: Assistance with Energy Tab Setup in Home Assistant
Hi,
I want to start by saying that I’m new to Home Assistant and home automation in general. I’ve been trying to set up the energy tab, but I’m struggling to get it working properly. For some reason, the Enphase system is reporting electricity production values that are consistently between 0 and 0.2.
I’ve searched the forums for solutions, but I’m still unable to resolve this issue. Any guidance would be greatly appreciated!
Thank you!
Enphase Software Version: D8.2.4264 (882efd)
Entities
Grid consumption: Envoy serialnumber Lifetime net energy consumption
Return to grid: Envoy serialnumber Lifetime net energy production
Solar production: Envoy serialnumber Energy production today
I use sensor.envoy_SERIAL#_lifetime_energy_production for the solar production; I’ve been told that the ‘today’ values are a hit & miss sometimes.
Not sure about the lifetime_net_production and lifetime_net_consumption values either - I have a non-Enphase battery and between charging the battery and feeding back to the grid, those values don’t make any sense for my setup.
Hi @oramospt, for the energy dashboard solar production entity for envoy best use the Envoy serialnumber Lifetime Energy production entity. We’ve seen multiple reports that the day value behaves unexpected, including not resetting to zero, late reset to zero and unexpected values. These are the miss & hit @chairstacker is referring to.
The energy dashboard will work fine with the lifetime value. Simply change it in the energy dashboard setup and you should be ok.
Clarification:
It’s not just the net part of the sensors that causes issues in my situation, the _lifetime_energy_consumption sensor shows this behaviour since mid-December last year:
I apologize for the late reply. I’ve tried what you suggested, but unfortunately, it didn’t change anything. I also tried serialnumber Energy production today , but encountered the same issue.
I’ve gone through multiple pages looking for a solution, but I haven’t been able to find one, perhaps because I’m still quite new to all of this.
If all is still failing then let’s have a look at some underlying data.
Is that still the case or are the values different now, but still not correct?
The evaluate what is going on I would need the HA Enphase_Envoy Integration diagnostics file and the HA log file with some hours of runtime with the Enphase_Envoy Integration. I don’t think you can post them here in a comment as files (don’t paste the comment as text in a comment) so send them in a DM. Or open an issue in for enphase_envoy in github.
To get the diagnostics file use the download diagnostics on the enphase_envoy device page
Let it run for couple of hours and disable debug again using same menu. That will then download the current HA log file. Remove anything you don’t want to share from it, but leave the enphase debug lines in. If tight on disk space on your HA device, keep an eye on it.
sum inv: the power reported by the individual inverters from /api/v1/production/inverters. This data may be between 0-15 min old. Sum of 5 inverters each reporting 200 - 225 Watt. Seems realistic number.
prd inv: also sum of inverters but from /production report, same value as sum inv
prod: value of the production current transformer from /production. This value is below 2.
mtr prd: value of the production current transformer from /ivp/meters/readings. This is typically source for previous mtr prd with some minimal time differences and also below 2.
Other columns are consumption values from same reports.
This is the raw data from the Envoy (and what you actually see in Home Assistant).
Seems to suggest that something is not correctly configured for the production current transformer. Almost as if it is reporting in kW rather then W, although that is just guessing.
No not really. We’ve seen reports for Envoy-metered without actual CT connected that had some unexpected behavior, but yours shows connected CT.
That’s why I have some suspicion about how the setup/configuration of the production CT or a quality issue of the CT. But as said, it’s a bit guessing.
