enphase envoy node-red issue

[hemant5400z]

Hi All,

I have bee running my Enphase for a while now, but looks like something strange happened. I pull the data using nodered and populate virtual device.
Is has bee working great for a while but all of a sudden i do see something strange.

on the ENphase web site i have WattsLifetime 18.8 MWh
but in my local device i see 15.5 MWh

See attached what i have in Domoticz database.
which is similar to what i pul from {"command":"udevice","idx":339,"svalue":"4305;15471673"}

but there seems to be a sudden drop anyone expriencing the same?

Thanks,
Hemant

Edit WaltervL: moved to separate topic as it is not related to the standard Enphase integration.

[waltervl]

Seems it is using power instead of creating ( meter values are going down...).
Are you extracting the correct values from Enphase with Node-red?

[hemant5400z]

Hi,

Yes this has been working for over a year.
I only have 2 values wattsnow and wattslfe

below is the node-red i have been using for over a year:
msg.payload = { "command": "udevice", "idx": 346, "svalue": msg.payload.wattHoursLifetime.toString()};
return msg;

Added some screenshots, making sure i'm not crazy


Hemant

[FireWizard]

Hello @hemant5400z,

There is nothing to worry about.

I see exactly the same.

My Enlighten website shows: 18.41 MWh, while my local webpage shows 10.4 MWh
If I poll http://{{{envoyaddress}}}/api/v1/production, I see: wattHoursLifetime: 10354129
So this address is more accurate than the local webpage.

I noticed the difference for the first time, after a software upgrade, done by Enphase.
I think they reset that specific counter after a firmware upgrade, but I do not know the exact reason.
See also: https://github.com/domoticz/domoticz/issues/5734 and various Enphase links.
We are definitely not the only one, who see that difference


So if this wattHoursLifetime value is very important for you, store it in a context variable in NR.

Regards

[hemant5400z]

Hi FireWizard,

Thank god i’m not the only one.
Problem is i use the watthourslifetime to calculate my actual anual production and my contract runs fron 18 feb until 17feb. This way i was able to do my anual production.

But now the whole calculation is messed up.
I need to figure out my production from 17th of feb until now but dont have the data anymore to so this.

How are you giys keeping track of annual production when it is not running from 1st of Jan? I cannot imagine that every contract with energy compleet any starts first day of the year.

Thank hope to have a smart solution in case enphase does a reset again

Would it be better do accumulate daily starting from contract date until now?

Does anyone have a script for this?

Thanks

[FireWizard]

Hello @hemant5400z,

I do not see your problem

As an example I show you 2 sensors:

Screenshot_Enphase_Compare.png (100.38 KiB) Viewed 666 times

Left you see the hardware device of Domoticz Enphase.
As far as I know, this sensor uses the "{ip}/production.json?details=1" endpoint.

Right you see a virtual sensor, that receives the data from Node-RED by MQTT.
My Node-RED flow uses as endpoint:"{ip}/api/v1/production".

You see a very small difference between those 2, but that is caused by the difference in time of the measurement.
See the time in "Last Seen". I poll my Envoy every 30 seconds, during day time.

So in fact, it doesn't matter how you do it.

Let's look to the log of both.

Screenshot_Enphase_Compare2.png (213.15 KiB) Viewed 666 times

You see above the graph for April 2025 of the Node-RED sensor (which is only 4 days old) and you see the counter gives a value of 10354.198 kWh
This is not the lifetime production, as that counter has been reset in between and I think more than once.

The production between April 1-4 has been 10354.198 - 10257.721 = 96.477 kWh.

Screenshot_Enphase_Compare3.png (195.52 KiB) Viewed 666 times

Above the graph for April 2025 of the Domoticz hardware sensor and you see the counter gives a value of 20663.436 kWh.

The production between April 1-4 has been 20663.436 - 20567.030 = 96.406 kWh.
the difference again is very small, only about 70 Wh.

But! You see that the counter of the Enphase hardware is in line with the lifetime of your installation.
It is even better than the value indicated in the Enlighten website.

So I very seldom look to the values indicated by Enlighten or the local webpage of the Envoy, but rely on Domoticz.
So it doesn't matter which sensor you compare. The result is more or less the same.

You can look up the counter value at Feb 18 2024 and Feb 17 2025. The difference is your production of last year.

But if you want to store it locally in a sensor, you can do that in Node-RED and send it to Domoticz.
See: https://flows.nodered.org/node/node-red ... nergymeter

I hope this explains something about the Enphase system and its indication.

Regards

[hemant5400z]

Hi,

You are correct my problem is with the annual calculation.

On mar 31st there is a negative of 2000 kwh.
The monthlybis fine.

Hemant

[gizmocuz]

I noticed the counter can reset sometimes in the Envoy.
Why not use the Domoticz build in support for Enphase?

[FireWizard]

Hello @gizmocuz,

I noticed the counter can reset sometimes in the Envoy.

Yes, and not only in your Envoy, but also on the Enlighten webpage (or in the Enlighten app).

Why not use the Domoticz build in support for Enphase?

The example above showed that it really doesn´t matter which endpoint you use, as long as you are not interested in the lifetime production.
The lifetime value from the Enphase API is not reliable, as you also concluded.

It is the best to use the Domoticz build in native support.

Long time ago the native build in Enphase support did not present the individual inverter values.
If you were interested in it, the only way to get these in Domoticz was to build it yourself, e.g. with use of node-RED.
That is why I still have both running and were able to compare.

I also use some other values to monitor the panels and the Q-relay.
So I fully agree. Use the native Enphase support in Domoticz.

[Edit] Currently I see again strange things, regarding the counters.
While yesterday, the daily production has been 32.652 kWh (which is normal), it is today already 9228.938 kWh
That is huge.
My node RED gives me -1173.762. So obviously something is going on with the counters
Oh, I have to pay

Regards

[hemant5400z]

Hi,

I want to keep track of the total based on contract. With this issue cannot use any of the counters as the lifetime is not reliable. Is there another option to calculate liftetime.

Cummulate daily and do a sum? The rest keeps chainching so cannot track this? This any ideas how to tackle this issue and get anual totals based on contract date?

Hemant

[FireWizard]

Hello @

As said before in the Domoticz native Enphase application:

You can look up the counter value at Feb 18 2024 and Feb 17 2025. The difference is your production of last year.

Or select any other date.

If you don't want that.
Create your own energy counter in NR.
see: https://flows.nodered.org/node/node-red ... nergymeter

Regards

[hemant5400z]

Hello @

As said before in the Domoticz native Enphase application:

You can look up the counter value at Feb 18 2024 and Feb 17 2025. The difference is your production of last year.

Or select any other date.

If you don't want that.
Create your own energy counter in NR.
see: https://flows.nodered.org/node/node-red ... nergymeter

Regards

Hi,

Native is fine with me, do you have a script that pulls the Total from de native plugin with startdate?

Cheers,
Hemant

[FireWizard]

Hello @hemant5400z

Sorry, I do not have such a script, but you can go to the "Log" and then to "Reports".
There you can select the data for each yesr and export it to CSV or XLS.

With the programs you can play with your data.

Regards

[hemant5400z]

Thanks!

Are you usering NR to populate the virtual sensor?

Hemant

[FireWizard]

Hello @hemant5400,

I use both the native "hardware" and a Node RED flow.
The reason is historical, as in the early days of the Enphase native "hardware", the application did not support
retrieving the data from the individual solarpanels/microinverters.

However, currently I have discovered a few times, that the native Enphase, stops updating its values.
This requires a restart of Domoticz. Don't know why, but the Node-RED flows continues.

Regards

[hemant5400z]

Hi,

I have seen similar issues so looking for a stable alternative, however in my case i'm also interested in the wattsLifetime and cannot use values from Enphase nor Native. so looking for something that calculates whats lifetime for me.

when i use the NR daily and look at the graph i have -2000 kwh for some days in may so, worthless at the moment.

Hemant

[gizmocuz]

@herman, you won't have this issue when using the native build in Enphase support in Domoticz.

[FireWizard]

Hello @gizmocuzm

@herman, you won't have this issue when using the native build in Enphase support in Domoticz.

What do you mean with "this issue"? Which issue?

Regards

[hemant5400z]

Hi Correct,

I dont' see this issue with native plugin like with NR:

However with native i don't have the Total per contract date which i has with NR but now also broken due to wrong values pushed. see earlier posts.
I want them al to work: Dayly Totals, Monthly totals and Annual totals by Contract date.

@FireWizard you don;s have the issue that daily's have strange numbers when pushing from NR to Domoticz as pervious post?

Cheers,
Hemant

[hemant5400z]

for NR I have always used this flow: