I just got an Enphase system activated and immediately connected it to Home Assistant, however there’s one big problem: The daily power production sensor is showing the lifetime power production instead, so it’s always the same value as the lifetime power production sensor. I tried to access the Enphase API directly to verify the numbers, but for some reason the particular one that contains this information always acts like I’m not logged in when I am.
So I guess the question is, is this an issue with the integration, or a firmware bug on my system? The web interface indicates that it’s running version D7.3.466.
2 Likes
I’m a newbie in Home Assistant, still trying to integrate things and understanding how all works together.
Just added my Envoy and noticed I only get production values for the panels. The Envoy values are zero or near zero. Since I couldn’t understand what could be causing this I searched around and found some old reports of this problem. It resurfaces from time to time. Not sure how to report it or to even confirm where is the problem
It seems to be a firmware bug with the Envoy system itself, reporting incorrect values through the web API. Mine was reporting the lifetime power production for the first week or two, then started reading 0 like most people report. The bug has been around for many months from what I gather and I really have no idea why Enphase doesn’t fix it.
In any case the current best workaround is to use a utility meter helper in Home Assistant to track the lifetime production (which still reads correctly) and reset on a daily basis. I can’t remember where I found the instructions for setting this up though and this also unfortunately keeps the units in MWh so normal dashboard display won’t show anything below 10 kWh (graphs are fine though.)
Thanks, i am happy I found this post.
I seem to see the same bug on a new European install after 4 weeks. Before mine was working OK, and now the “Envoy Energy Consumption Today” starts at a random value above 400 somewhere around 1:00 hours, instead of 0 kWh at exactly 0:00 hours midnight.
I shall try to make a “template value” or helper to fix this Envoy bug.