Closed ericstewart22 closed 1 week ago
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!
(message by CodeOwnersMention)
enphase_envoy documentation enphase_envoy source (message by IssueLinks)
Hi @ericstewart22, recommendation is to use the lifetime energy production value for the energy dashboard. Day values have been reported as less reliable and prone to surprises, like in your case.
The problem
After a power outage, the Enphase Envoy Energy Production Today sensor reports incorrect values of 5,000 kWh-16,000 kWh for a period of time. This causes issues with the energy dashboard. I would suggest that the output from this sensor pass through a range sensor for reasonable values.
What version of Home Assistant Core has the issue?
2024.5.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Enphase Envoy
Link to integration documentation on our website
https://www.home-assistant.io/integrations/enphase_envoy/
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
In my case, it stopped receiving information. I was restarted Envoy to no avail. I know enabled debug logging on the integration...
Hi @DavidAtGoliathResearch, do you have the same problem (spikes in todays production after power outage) or a different one? From your description it sounds as if you can't connect to the envoy after power outage. If the first, make sure to use the lifetime energy production value in the Energy dashboard. If the latter please create a separate issue and not add a different issue here.
Sorry, yesterday I couldn't even connect to the Envoy, but today I got information from yesterday and today. I still need to compare the information against Enlighten to see if they match. It is not the first time I suffered a power outage, but it was the first time Home Assistant stopped receiving information from my Envoy IQ7. So, even if the issue is not exactly the same, the reason was the same. If my values match, something I should know by the end of the day, I could create a different issue.
Thanks,
David
From: Arie Catsman @.> Sent: Wednesday, June 12, 2024 3:08 AM To: home-assistant/core @.> Cc: David Izada-Rodriguez @.>; Mention @.> Subject: Re: [home-assistant/core] Enphase Envoy Production Today sensor values after a power outage (Issue #118729)
Hi @DavidAtGoliathResearchhttps://github.com/DavidAtGoliathResearch, do you have the same problem (spikes in todays production after power outage) or a different one? From your description it sounds as if you can't connect to the envoy after power outage. If the first, make sure to use the lifetime energy production value in the Energy dashboard. If the latter please create a separate issue and not add a different issue here.
— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/118729#issuecomment-2162269144, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS2FH7ZHV3GR7QCPSHV475DZG7XV5AVCNFSM6AAAAABIWUKKPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSGI3DSMJUGQ. You are receiving this because you were mentioned.Message ID: @.***>
@ericstewart22, @DavidAtGoliathResearch, as there's no further reply can we close this one?
Sorry, after the last few days following the power outage, the connection to the Enphase panel failed for some reason and I found differences against Enlighten. With this information you can decide if the case should be closed.
Thanks,
David Izada Rodriguez
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Arie Catsman @.> Sent: Saturday, June 22, 2024 5:10:32 AM To: home-assistant/core @.> Cc: David Izada-Rodriguez @.>; Mention @.> Subject: Re: [home-assistant/core] Enphase Envoy Production Today sensor values after a power outage (Issue #118729)
@ericstewart22https://github.com/ericstewart22, @DavidAtGoliathResearchhttps://github.com/DavidAtGoliathResearch, as there's no further reply can we close this one?
— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/118729#issuecomment-2183955020, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS2FH7266FNF34PDGJLLFC3ZIU5QRAVCNFSM6AAAAABIWUKKPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBTHE2TKMBSGA. You are receiving this because you were mentioned.Message ID: @.***>
@ericstewart22, what firmware is your Envoy running? If it's version 3.x there's a fix in the making. If the fw is newer I would need a debug log file with enphase_envoy debug enabled that catches a power outage/restart of the Envoy to apply a similar filter.
Thanks for following up. I have an IQ Gateway (SKU X-IQ-AM1-240-3-ES) and the firmware is D7.3.621. I am not sure if the fix in the making would apply to my device. The workaround/solution suggested above has been working for me for the time being, thankfully. In case it's useful, I have my device connected via ethernet so the communication should be very reliable.
Thanks for the feedback @ericstewart22. With your firmware version the solution is indeed to use the lifetime value, the day value has been reported multiple times with this awkward behavior.
@home-assistant close
The problem
After a power outage, the Enphase Envoy Energy Production Today sensor reports incorrect values of 5,000 kWh-16,000 kWh for a period of time. This causes issues with the energy dashboard. I would suggest that the output from this sensor pass through a range sensor for reasonable values.
What version of Home Assistant Core has the issue?
2024.5.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Enphase Envoy
Link to integration documentation on our website
https://www.home-assistant.io/integrations/enphase_envoy/
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response