Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Production solaire lifetime going down and not conform to value in englithen #203

Open
seblang opened this issue Aug 21, 2024 · 9 comments

Comments

@seblang
Copy link

seblang commented Aug 21, 2024

since the 26 july 2024 my sensor from lifetime production is going down instead of growing !
HA envoy

I do not understand why and what I can do to solve this!!

engliten envoy

@catsmanac
Copy link
Collaborator

That is a strange pattern @seblang. As the data for Production solaire lifetime comes directly from the Envoy itself it must be something on the Envoy.

You can validate the raw data send by the envoy by downloading a diagnostic report from Home Assistant,
afbeelding

In the downloaded json file look for lines with "Endpoint-. These contain the last data retrieved from the Envoy.

Feel free to upload the json file here if you want me to have a look at the values before you take any actions.

As this data is reported by the Envoy, an option to consider is the restart the Envoy box. Maybe that clears the situation, maybe not. Otherwise reach out to your Envoy or installer about this

@seblang
Copy link
Author

seblang commented Aug 21, 2024

Hi @catsmanac

first tank you for the answer.
Yes the value in json are consistant with HA :

"Endpoint-production_v1": "{\n "wattHoursToday": 14102,\n "wattHoursSevenDays": 88897,\n "wattHoursLifetime": 211131,\n "wattsNow": 0\n}\n",

It's strange! I have restarted the envoy box and will see tomorrow if something change!

I will ask enphase but before I will check if it's possible to have the info with an API
have a nice day

@catsmanac
Copy link
Collaborator

Ok, so the envoy is envoy standard, not a metered one and no current transformers?

As for the API, Enphase published:

The PDF's from these 2 sources:
Envoy-API-Technical-Brief.pdf
IQ Gateway Local API or UI Access using Token-TEB-00060.1.0-EN-2023-08-14.pdf

@pipje2001
Copy link

I'm having the same issue since a couple of months, this is my parents HASS setup so don't check it too often and i guess they havent noticed before.
2024-10-30 11 43 50 home kolmol nl 7419d4eb0126

This also makes the energy dashboard completely unusable:
August:
2024-10-30 11 44 07 home kolmol nl c80611e697ed
September:
2024-10-30 11 44 16 home kolmol nl 7635ef09f358
October:
2024-10-30 11 44 24 home kolmol nl e95c5ae0f8ef

Any idea on what might cause this? And if there is a way to restore the energy dashboard?

@catsmanac
Copy link
Collaborator

Is the lifetime value going up between those down steps? Or is if same value always and going down every now and then? (zoom in on a time period without a large change to see it)

For the energy dashboard you could try using todays energy production value. Normally I don't recommend using it, but you could see how it does.

Is there any errors in the log file?

@pipje2001
Copy link

pipje2001 commented Oct 30, 2024

It does go up between the steps, in an expected manner. Is this value coming from envoy directly? As in, is it also jumping down in the envoy system?

There is nothing related to envoy in the logs, but I assume that if there were something it would be when it jumps down.

@catsmanac
Copy link
Collaborator

Yes the value comes from the Envoy itself.

We can try if we can see what happens by enabling debug for the Envoy in Home Assistant until one of those changes happens. That will grow the log file quite a bit as it seems the changes are days apart, so if diskspace is an issue you need to keep an eye on it and if it grows too big simply delete it so HA continues with a new one.

afbeelding

@pipje2001
Copy link

Will do!

But if its coming from envoy, then how would the debug logs know why its gone down?

@catsmanac
Copy link
Collaborator

Probably not, but it will allow to rule out any other issues and see if there's any pattern or correlations to other data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants