Domoticz

Hi folks,

This issue is not directly related to Domoticz or my own installation, but I see this issue with 2 installations from friends.

I notice that Enphase envoy (with firmware D7.0.88 (5580b1)) is resetting the whLifetime property in https://local-ip/production.json to 0 (zero). The cloud (and App) are still reporting the correct value.

Does anybody has this issue of does know how to fix this (perhaps firmware update?)

Let me know, as currently we are in the dark with this issue.

Hi,

And what does https://local-ip/api/v1/production show?

I noticed before, that if you power down the Envoy, the maximum production of the induvidual inverters are reset, but did not see it for the total (lifetime) production.

And I saw it one or two times, that it was done by Enphase, but I do not use v7. I'm still on version 5.

Regards

Thanks FireWizard for your reply.

Also when checking the endpoint /api/v1/production, it report all zero values

{
"wattHoursToday": 0,
"wattHoursSevenDays": 0,
"wattHoursLifetime": 0,
"wattsNow": 0
}

Hi @reinos,

Strange. I.m.o. it should not give all zero's.

I see in my Envoy:

"wattHoursToday": 30011,
"wattHoursSevenDays": 138409,
"wattHoursLifetime": 7474194,
"wattsNow": 0

It is dark now, so the values look normal.

If you enter the IP address only, what does the Envoy show?

Regards

Once again, my system with the newer Firmware is working fine though

When I just enter the IP we can login into the system and we see the new values after the reset. Also the /production.json endpoint shows the value after the reset. However, in the endpoint /v1 it show just 0 values.

To summarise this.

https://enphase.local/production.json return a new value for whLifetime. It was reset to zero and it is now counting up.
https://enphase.local/ shows the same values as /production.json
https://enphase.local/api/v1/production shows all 0 values.

I have the same issue.

In domoticz it uses the "incorrect" wattHoursLifetime from enphase. Now my data in Domoticz is more or less useless.


I posted some information on the enphase forum. I am unable to post links here. So I cannot share my more detailed analysis.
Does anyone know how to fix this at the Domoticz side?

I tried fixing values in the database, but after restarting Domoticz it receives the incorrect wattHoursLifetime from enphase. In Domoticz this results in a huge negative spike in the graphs. It just calculates the difference between the previous counter value and the incorrect received wattHoursLifetime from enphase.

Any help would be appreciated

I tried this fix in the domoticz database.

Please make sure to create a backup first!

My incorrect value is only in the meter_calendar table (it is more than 7 days ago).

I ran 2 queries in the database:
1. Query to change the incorrect value to the correct value (= value from enlighten app). Since this is 1 value, it can be changed manually as well
2. Updated the counter value. I substracted the amount that was caused by the reset to 0. So all counters before the date I changed to counter = counter - gapvalue.

Commit everything to the database and start Domoticz again.

This way all the graphs in Domoticz are correct EXCEPT one: the compare usage graph at the bottom of the page.

I do not know yet why this is incorrect. Perhaps this is calculated daily, or it does not work with negative counter values.