Domoticz

Indeed, today the counter gives a normal value, thanks.

Hi all,

I have some doubts about the counter of device "Enphase kWh Production" based on the native Enphase hardware application.
Where does it get it's data from? Is it gathered from "http://envoy/production.json" ?
Which counter is used?

Below my Enphase devices.
I own 14 solarpanels, for the example I use both Enphase hardware applications (Native and Python Plugin).
I have already merged the solarpanels to the Native Enphase hardware application (so I only have 1 set of 14 solarpanals which receive their data from the Native Enphase hardware). I still though have the 2 counters.
The device named "Enphase kWh Production" (which is a counter of type general) is from the Native Enphase hardware application.
The device named "Enphase Envoy - Total" (which is a counter of type P1) is from the old Python Plugin hardware application. In the screenshot below a snapshot which is taken at the same time (10:59:42 hour).
Here can be seen that the old Python Plugin shows the same wNow (762Watt) as the Enphase Envoy Metered-S from its actuals (production.json).
When I add up the counters of the individual panels I also have 762Watt.

Where does the 1099Watts comes from within the Native Enphase hardware application?



.

Hi,

Anyone else experiencing the same error with the Native Enphase Envoy hardware: The hardware works ok for a few hours and then appears...
After disable and then re-enable the hardware makes it working again for some time (without changing the token in the variables)
Restarted the hardware around 13.50 today
and now again error:

Since this morning I got the error, Error: EnphaseN: Invalid data received! (no session_id). before it did work. A update?

still same issue here, In hardware tab I know set "Data TImeout" to 5 minutes so the hardware in Domoticz automatically restarts. Not the best solution but for now it works to keep Enphase up and running in Domoticz.

Xavier82 wrote: ↑Thursday 15 February 2024 9:28 still same issue here, In hardware tab I know set "Data TImeout" to 5 minutes so the hardware in Domoticz automatically restarts. Not the best solution but for now it works to keep Enphase up and running in Domoticz.

Indeed not the best, but if it will help, oké. I will turn it on.

3 days ago the Envoy stopped publishing data to Domoticz. In log indeed the above mentioned Invalid data received! (no session_id) message. After logging in manualy to Envoy I was asked to generate a code. According to the Domoticz wiki I entered this code in de Domoticz user variable and after some minutes Domoticz started to report actual data again.

But.... it started with a negative value, see the sceenshot attached. In the data dump from Domoticz is no negative number, just to me logical higher values because envoy couldnt publish it data for a few days. See attached xls.
My question is how to " normalize" the data as it has impact on all graphs.

Good question @HansSch....
I saw this negative value also, thats the reason why I set the data timeout to 5 minutes to prevent this.
When restarting the hardware there is no need for a new code, it just works with the old code.

Thanks @Xavier82. The restart after 5 minute option did not solve my issue. Thats why I renewed the key.
Still the question how to normalize the data. Enyone?

Until last Thursday I was working with a DzVents script to read the data from my Envoy into Domoticz. That worked fine from 2020 with firmware version 5.0.55 on the Envoy. Last Thursday evening an update took place (unsolicited) to firmware version 7.0.88. From that moment on, nothing enters Domoticz anymore.

After some googling I understand that the native Domoticz solution also works under firmware 7.xxx
However, I can't get it running. I followed the instruction from: https://www.domoticz.com/wiki/Enphase I now get this error message: 2024-03-19 00:07:51.902 Error: envoy: Invalid data received! (no session_id)

I am using Domoticz version 2024.4 on a clean install on Raspberry Pi4
Envoy is meterd however I not using the counterrings.

What I have already tried:
Enter username and password
Leave username and password blank and enter installation ID
In both cases the wired IP address of the Envoy is used with port 80.
Restarting Domoticz
Rebooting Pi

No luck in either case. Hardware is created, but no devices.

Are there any geniuses here who have had this problem and were able to solve it?

@Copitano:

Did you supplied the key to the Uservariables?
Username and password (from the website: https://enlighten.enphaseenergy.com/ must be entered.
Make sure "poll inverters" is also enbaled in Domoticz hardware setting of native Enphase.

@ Xavier82
Yes I tried all of that, except with the right username. Using the one of my installer account instead of my user account worked.
Thank you for your question. It made mi think it over again and think of my installer account.

Now I'm curious how long the token will continue to work, or will it be automatically renewed over time?

HansSch wrote: ↑Sunday 03 March 2024 17:35 Thanks @Xavier82. The restart after 5 minute option did not solve my issue. Thats why I renewed the key.
Still the question how to normalize the data. Enyone?

To get rid of the negative value from the chart:-
Hold down the shift key and click on the rogue entry on the chart, a pop-up should appear asking if you want to delete this entry.
Click OK, the entry should disappear from the chart. It won't correct any missing data that's caused it to appear, but at least it won't be there.

I had to do this after Enphase upgraded my Envoy-S-Metered from 4.10.35 to 8.2.4264. In the Domoticz hardware page I had to change the Envoy from port 80 to 443, I also put my Enphase website login credentials here after the initial token ran out (more on that later). In More Options -> User Variables there were two blank EnphaseToken_ entries, I web browsed to my inverter, from there followed the link to get the token, then pasted this into both blank entries.

At least I'm not stuck on build 15369 any more (this appeared to be the last to support data from 4.1.0.35).

Tokens don't seem to last very long, at least under V8; my first one only lasted about 24 hours, the second one has now expired (I just copied it from Domoticz back to the Envoy login page and it rejected it) but presumably Domoticz is now using the username/password entry instead, as the Envoy also gives the option to use Enphase credentials and Domoticz is still getting data from it.

If you're on a regularly restarted or regularly updated Domoticz build it'd be worth checking after each restart/update that it's still getting fresh data from the Envoy. If the devices on the Utility screen look like they've stopped getting data while the rest carry on, you might need to re-key or try giving it your Enphase login.

Hi All,

I just noticed as of september it looks like the node-red connection which pushes data to Domoticz enphase is updated/broken I don't receive any more ata the switch is stalled. Do others have the same issue or a fix?

api/v1/production/inverters
msg : string[16]
"JSON parse error"

when i go to my local envoy and try to login it keeps asking for a token, i tried to use the token in Dmoticz user variable but wrong token.
How do i get the correct token? It seems the Domoticz plugin is able to read the individual inverters.

I have Ephase ENvoy standard I was able to pull data for almost a year

Thanks in advance.

Hemant

This topic is about the native integration of Enphase, not the Node-Red route.

Hello @waltervl,

You wrote:

This topic is about the native integration of Enphase, not the Node-Red route.

I have never been aware that a specific thread is only dedicated to a specific solution.
I think it is important, that users have multiple options to achieve their goal.

If this thread would be only about a specific solution, then that would not be the native solution, because at the time this thread has started
(March 2020) the native solution only presented the general Solar production and not the production of the individual inverters. Also the
username/password was not needed for the general production (only an installer password for the individual production)

Nowadays I would prefer the native solution, but as said it is good that users can choose.
And your response does not help the user Hemant.

So I take the freedom to answer his question.

@hemant5400z

For a flow, send me a PM. The flow is too big, to post it here.

Regards

It is a little complicated for users to mix up different solutions in one topic....

Since january the 10th 2025 the following error: "Error: Enphase: Error getting http data! (info)"

More people who encountering this problem?

Maybe you have a token for a year? Try a new token?
No issues here...

gizmocuz wrote: ↑Wednesday 15 January 2025 15:22 Maybe you have a token for a year? Try a new token?
No issues here...

Sorry, totally forgot to post a update. The problem was a OpenVPN client update (OMV NAS).

My NAS is connected to PIA and since the last OpenVPN client update my enpahse, which is on a different VLAN, could not connect anymore to the NAS. I had to put in "route 10.0.10.0 255.255.255.0 net_gateway" (my VLAN subnet) in my OpenVPN config. Before this wasn't necessary.

So we are up and running again.