Enphase Envoy's "Current battery discharge" sensor has incorrect values

[joergbattermann]

The problem

Good morning,

I haven't used the " Current battery discharge" until trying to use it just now and I noticed that its values are consistently off by 1 kW or so from what Enphase (Enlighten) reports (and also what the individual batteries' *_power sensors cumulatively report), see i.e. this:

or this:

... and the charge rates aren't fluctuating right now, meaning the number of that " Current battery discharge" sensor has been off by those several hundred watts consistently this morning. The batteries have not been charging at >4 kW the entire morning so far as per Enlighten, and yet that HA sensor says it has for a while now.

Maybe I am looking at the wrong sensor to see the aggregate batteries (dis) charge, but if it's supposed to show what goes in and out of them, then it appears it's not reading/providing the right value(s), at least not compared to Enlighten.

Is that a bug or am I using it wrong?

Thanks!

What version of Home Assistant Core has the issue?

core-2024.6.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

enphase_envoy

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[joergbattermann]

Some more info / update here: I also noticed that this particular sensor never really reaches / stays at or anywhere near '0kW', even though we are at 100% SoC usually around noon and then stay there for the rest of the afternoon (with the occasional 'dip' where the Enphase System charges another few wH for a minute or two). That particular sensor is during that time of the day always sitting at -1.something kW:

and

And semi-live / right now-ish it looked like this:

[home-assistant]

Hey there @bdraco, @cgarwood, @dgomes, @joostlek, @catsmanac, mind taking a look at this issue as it has been labeled with an integration (enphase_envoy) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of enphase_envoy can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign enphase_envoy Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

enphase_envoy documentation
enphase_envoy source
_{^{(message by IssueLinks)}}

[catsmanac]

Hi @joergbattermann, can you upload your diagnostic file here after downloading it from HA

As the Storage CT is a recent add to the data, it would help if you can provide a couple of hours of debug log file for Envoy data collection while battery is charging/discharging to verify original assumptions on this.

[joergbattermann]

I turned debug logging for the last 1-2h of batteries charging earlier today.. and then about another 1-2h of them being mostly at 100% SoC during the afternoon... and I'll turn debug logging back on when we go into the evening and night to record / debug log what's happening and logged during the nightly discharge phase and will come back tomorrow with both files and also going to pull the Enphase Enlighten report data for today.

Is there any way to safely exchange files without exposing them permanently on the internet as part of a github issue & -discussion? I can gladly provide a temporary link which I can turn off once you confirmed you have the file, but if there's a usually used way to exchange those, lmk.

Thanks again @catsmanac !

[catsmanac]

Is there any way to safely exchange files without exposing them permanently on the internet as part of a github issue & -discussion?

I'm not really into how to do that, only method here I can think off is dropping the file here, me downloading it and you editing the topic again and removing the file again. But I'm not sure if that will remove the file also from the place where it was stored on github.

So if you have a method we might best use that.

[joergbattermann]

Ok will provide a shared link and we can do that (you letting me know once you got the file) - thank you! It's just before midnight here right now and I've had debug logging enabled as of circa 2-3hours again for the discharge phase.. but to give you a bit more/longer data, I'll just leave debug logging on overnight and provide the file from earlier today and this one in the morning.

[catsmanac]

Thats fine, thanks. Sleep well

[joergbattermann]

As I had mentioned, I kept debug logging on overnight until about 9:25am this morning, so you'll see the discharge dip down to about 43% or so this morning and then start going back up when the sun came out, see below. I was also trying to get the report from Enphase Enlighten, but somehow the data is not available there and I got to submit a support ticket with them first... so all I got is the graph representations below.

Either way, let me know if and what else you might need.. and thank you!

And this is what the graph as per Enphase Enlighten looks like for yesterday & this morning:

[joergbattermann]

Oh and here's the graph of the 'IQ Combiner 5 Current battery discharge' for the same time frame.. in which you can see that despite being at 100% SoC, the sensor says we had a somewhat continuous ~ -1.2kW reading on that sensor between noon and 7-8pm yesterday:

[catsmanac]

Thanks @joergbattermann , I just downloaded then successfully so you can close it again. Time for some number crunching. I'll keep you posted.

[joergbattermann]

Appreciate it, thank you @catsmanac !

[catsmanac]

Hi @joergbattermann, looking at the raw Envoy data there's indeed an offset in the Storage CT power reading. There's another battery power entity reported, real_power_mw which reports power from the battery data while current battery discharge comes from the Storage CT.

When I compare both, they have the same overall profile, but offset as you noticed. The Energy charged amount also slowly increases over the day while SOC is at 100.

So this is data reported by the Envoy. I think Enlighten app is using data from the batteries itself as they have access to way more data as we have. One would be inclined to think the Storage CT is not zeroed correctly, is picking up some noise or alike resulting in the non-zero value at rest. Might want to check with your installer if he can see what's going on.

I have all your data in a text file with only timestamps and values. Let me know if I should upload it here if you want to see it or in some other way.

Daytime power log

Nighttime power log

When comparing the battery SOC reported by ensemble and the Energy charge/discharge reported by the CT one can observe a continued amount of energy charged reported in the day when SOC reaches 100

Daytime energy changes

Nightime energy changes

[catsmanac]

Some side-notes from your data:

• Your Envoy switches every now and then between 2 IP addresses. I assume it's probably both on wired and WIFI. Depending on timing / order when it announces itself HA will switch to the other one. It's not an real issue unless one of the connections is shaky. In your case I see no real disturbances.
• Shortly after 11 PM there's a brief communication outage. That's a known behavior where the Envoy resets something internally or so and causes a timeout to happen. It happily resumes after it.