enphase envoy with (HTTP) interface

[hemant5400z]

There have been made some changes recently and it is now also possible to use V7 with the native Enphase implementation in Domoticz

Hi,

I'm just installed the 2022.2, but the Native plugin does not provide me with Username/password option.

Hemant

[FireWizard]

Hi @hemant5400z,

For that, you need the beta (newer than 14773).

See: https://www.domoticz.com/wiki/Domoticz_ ... _-_Commits

Regards

[SumDum]

Does anyone here have panels facing in two directions? e.g. East & West.

I do and I've found domoticz does not always correctly assign data received from the api to the meter devices. If all your panels face the same way and so always produce roughly the same power you won't be able to tell you are getting the wrong data logged.

If anyone does have panels in more than one direction could they please verify their inverter data is correct? There's an issue open on github showing the problem.
https://github.com/domoticz/domoticz/issues/5555

Thanks
SumDum

[FireWizard]

Hello @SumDum

I try to understand what your issue is, but I do not understand your issue.

Each Enphase inverter is individually connected to a Solar panel and each Enphase inverter has a unique serial number.
If you request the API of the Enphase Gateway you will receive an array of all inverters and each element looks like:

{
"serialNumber": "121851003477",
"lastReportDate": 1675347243,
"devType": 1,
"lastReportWatts": 6,
"maxReportWatts": 122
},

So in the response is a direct relation of the "serialNumber" and the "lastReportWatts"

This response has nothing to do with the orientation (East, West or even UpsideDown)
Of course, panels facing East will produce more power in the morning than panels facing West.
In the afternoon it is the other way around, while panels facing South will produce the most of their energy around noon.

You cannot compare panels with each other, even not if they face the same direction. There are always effects of shadow, polution, etc, that will give minor differences.

You should check whether the indication in the Domoticz widget is identical to what is shown in the browser, if you go to:

Code: Select all

http://192.168.10.40/api/v1/production/inverters

Only if you see a difference between, what is shown in your browser and what is shown in Domoticz, you can conclude that there is something wrong.

Regards

[SumDum]

Hi FireWizard, thank you for your response.

You should check whether the indication in the Domoticz widget is identical to what is shown in the browser, if you go to:

Code: Select all

http://192.168.10.40/api/v1/production/inverters

Only if you see a difference between, what is shown in your browser and what is shown in Domoticz, you can conclude that there is something wrong.

Which is precisely what I do see!

If you look at my last post on github I have the latest beta installed on two Pi Zeros and I have posted screenshots of them both. Take for example my south facing panels which consistently produce the most at this time of year.

In both Pi Zeros panel 122101023471 is producing 55 watts. All good.
The second south facing panel is 122101029000. That is showing 6 watts in one Pi Zero and 57 watts in the other. The panels are adjacent and the api output always shows them almost matching, 57 watts is the correct number. The incorrect pi zero is pushing all inverters over MQTT to NodeRed, it delivers the wrong data against serial number 122101029000, 6 watts at this instant.
So where has the missing 57 watt reading gone? It is assigned to a totally different inverter on an East facing panel, at the time I took the screenshots my four East facing panels were producing ~32 watts, how did one of them get 57 watts recorded?

Something is going wrong. Both Pi Zeros are reading the same data from the Envoy. My original Pi Zero is mixing some the readings up, assigning them to the wrong widget and MQTT push. The second Pi Zero is doing everything correctly.
I could just move the MQTT push to the second Pi Zero but how long will it be until that one starts mis-recording the data?

[FireWizard]

Hello @SumDum

This explains a lot more, but I do not believe, it has something to do with the orientation of the panels.
If, it is true, it may happen randomly.

You do have a clear picture of the panel lay-out and know exactly where each panel (serial number) has been installed?

I have the latest beta installed on two Pi Zeros

How many devices are polling the Enphase Envoy (Gateway)? Are the 2 Pi Zero the only two devices?
Keep in mind that polling the Enphase Envoy to frequent with two many devices, this may crash the Gateway.

In my opinion 1 poll per 30 seconds is enough.

Are the two Pi zero's identical? Obviously 1 Pi Zero functions correct and the other show a failure, You also said:

The incorrect pi zero is pushing all inverters over MQTT to NodeRed

Where is Node-RED running, also on the Pi Zero?

Is the load of the Pi Zero identical?

Why don't you connect your Node-RED to the Enphase Gateway and push a MQTT value to a virtual sensor in Domoticz on the Pi Zero.
I do that already for many years and had never any issue.
See: viewtopic.php?t=29331

[SumDum]

Hi FireWizard,

Hello @SumDum

This explains a lot more, but I do not believe, it has something to do with the orientation of the panels.
If, it is true, it may happen randomly.

I only mentioned the orientation of the panels because if all panels faced the same way I would not know anything was wrong. At the time I took the screenshots in github:
South facing panels (2 panels) were producing 56 watts +/- 1 watt
East facing panels (4 panels) were producing 32 watts +/- 1 watt
West facing panels (7 panels) were producing 7 watts +/- 1 watt

So when Domoticz tells me an east facing panel is producing 57 watts I know something is wrong

You do have a clear picture of the panel lay-out and know exactly where each panel (serial number) has been installed?

Yep, careful notes were kept when the installations were done. I know they are right because I did all the installation myself. Enphase inverters have peel off serial number labels on them and they provide a plan so that it is very easy to keep track. I can post .PDFs of the installation maps.

How many devices are polling the Enphase Envoy (Gateway)? Are the 2 Pi Zero the only two devices?
Keep in mind that polling the Enphase Envoy to frequent with two many devices, this may crash the Gateway.

In my opinion 1 poll per 30 seconds is enough.

Now there are two Pis and an occasional manually refreshed browser tab. When I first suspected a problem there was only one Pi Zero. B+ (see below)

Are the two Pi zero's identical? Obviously 1 Pi Zero functions correct and the other show a failure, You also said:

Ah no, I made a mistake here. The original Pi reports:

Code: Select all

Model           : Raspberry Pi Model B Plus Rev 1.2

And the second one:

Code: Select all

Model           : Raspberry Pi Zero W Rev 1.1

Neither are in sight but that's no excuse

Where is Node-RED running, also on the Pi Zero?

No, that's on a Pi 4 totally separate.

Is the load of the Pi Zero identical?

The Pi B+ has one DS18B20 attached, plus the Enphase stuff.
The Pi Zero has five DS18B20 attached plus it now has the Enphase stuff.
Neither are running other services. So really, not much difference, I'm a one box - one task kinda guy.

Why don't you connect your Node-RED to the Enphase Gateway and push a MQTT value to a virtual sensor in Domoticz on the Pi Zero.
I do that already for many years and had never any issue.
See: viewtopic.php?t=29331

Really because that looked complicated, I never found the time to work through it. Then the beta turned up & made it so much simpler

SumDum

[FireWizard]

Hello @SumDum,

I made a test with my old Raspberry Pi, which I usually use for testing. This test Pi is running version v15018, so the latest beta.
I compared the results that has been received by the test Pi with my production result. This production result comes directly from Node-RED, as described in viewtopic.php?t=29331.

I do not see any difference between these two, where the test Pi, which is a Pi 1B (Raspberry Pi Model B Rev 2), handles the Enphase Envoy hardware with the individual panels enabled and my production system receives the individual data directly from Node-RED.
Poll frequency is 1 per 30 seconds.

I do not see any difference between these two. I have only 8 panels, facing south.
So I'm still not convinced that it is a bug in the Enphase software in Domoticz.

Could it be caused by you Pi Zero W?

Regards

[SumDum]

I'm not ruling anything out FireWizard.

I know that when I first set up the B+ I had no reason to suspect a problem. All the Inverters were imported with a bare serial number as their identity, there was no 'Inv: ' prefix you now get. I edited all their names prefixing their position to make them meaningful such as "122117033377" was changed to "GE1 122117033377", first panel in the Garage East array etc. Everything worked fine, as the sun rose and travelled across the sky domoticz reported sensible and consistent numbers for the panels in the South facing, east facing and west facing arrays.

Then I installed build 14975. Within a day I noticed:
- A discrepancy between what my two south facing panels were reporting
- One East facing panel reporting more than the other three.
- One out of seven west facing panels reporting zero

I checked the /api as initially I thought a West inverter had died. Inverter death was plausible as the East & West arrays were new so I could well be on the down slope of the bathtub curve. Plus I'd had two power cuts. But no, the /api reported it working just fine while domoticz insisted on zero production.

Today I've added my two retired inverters to the B+. These are still in the json every scan with zero values (don't ask me why, ask Enphase!) yet Domoticz reports one produced power today. It's on my desk in front of me. It hasn't been connected to a panel in over a year. Hmmmm.
So domoticz says an inverter on my desk produced today and an inverter that the api says is working fine domoticz reports zero for. Do I disbelieve my eyes and the /api or domoticz?

I'm just trying to find out how domoticz handles the json data it reads. Is the json "serialNumber" pattern matched against the widget (device) names every scan? Does it assume the Enphase delivers the panel data in the same order each time and assign to the widgets in the same order every time? Something else involving the ID? If I can understand what domoticz is trying to do I might me able to hazard a guess at what is going wrong. My C is not up to understanding the code. Maybe something got mucked up in the database when 14975 first ran. Or the power cuts caused corruption. I think not because I've tried restoring to before the power cut and to before the first observed problem. I first observed a problem in the first build I ran that included this change:

Code: Select all

14969 	20230117 	Enphase 	Setting inverter device types to computed 

That changed the way inverters were handled and if my reading of the code is correct there's a 'first time' code path that would run for new inverters or for existing inverters first run of the new code. My C is not nearly good enough to be sure that's correct.

Next time the sun shines here I'll take another screenshot of the B+ & Zero showing different values for the same serial number if I can capture the json as well I will. It needs to be sunny & early or late in the day so that there is marked difference in what the orientations produce.

It could be the Pi B+ is doing something different to the Pi Zero due to a hardware bug but let's be honest, a software fault is more likely. The B+ is parsing the json fine, all the right values are shown in domoticz but some of the values are against the wrong device.

[FireWizard]

Hello @SumDum

Today we have a little bit more sun than yesterday. I compared the results in the Test Pi with the production Pi, but did not record any difference.
So again no issues observed. Just upgraded to the latest beta (v15022)

I have both test and production set to " To Computed" and I do not believe that will influence your result.

Like you, I do not believe in a hardware bug.

You can compare the results with the flow below, which you can install on your Pi4.
This flow does not use any part of the Domoticz software. It reads the API and outputs data to Domoticz (MQTT) or a "Debug" Node.

Screenshot_Enphase_Inverters1.png (33.31 KiB) Viewed 18624 times

The left Inject Node triggers the flow every 30 seconds. It is up to you to change it.
The next "Day Time Switch" opens the flow from 1 hour before sunrise until 1 hour after sunset.

The HTTP request node polls the API Envoy (Gateway).
You have to set the foolowing parameters yourself:

1. URL. Use your own IP address
2. Username. In my case "Envoy"
3. Password. Last 6 digits of the Envoy (Gateway) serialnumber

Screenshot_Enphase_Inverters2.png (43.31 KiB) Viewed 18624 times

The next node splits the data, so that we have one message per inverter.
The "Function" node sends in to the correct Domoticz iDX
You should do the mapping yourself.

Try it and compare.

Code: Select all

[
    {
        "id": "32228b5e.6bbbe4",
        "type": "inject",
        "z": "fa8c9e54db2d0f2a",
        "name": "Timer ( 30 seconds)",
        "props": [
            {
                "p": "payload"
            }
        ],
        "repeat": "30",
        "crontab": "",
        "once": true,
        "onceDelay": 0.1,
        "topic": "",
        "payload": "",
        "payloadType": "date",
        "x": 220,
        "y": 300,
        "wires": [
            [
                "4709b3cb.376b2c"
            ]
        ]
    },
    {
        "id": "4709b3cb.376b2c",
        "type": "time-switch",
        "z": "fa8c9e54db2d0f2a",
        "name": "Day Time switch",
        "lat": "52.179281",
        "lon": "5.606528",
        "startTime": "sunrise",
        "endTime": "sunset",
        "startOffset": "-60",
        "endOffset": "+60",
        "x": 460,
        "y": 300,
        "wires": [
            [
                "1bf22be8.529d6c"
            ],
            []
        ]
    },
    {
        "id": "1bf22be8.529d6c",
        "type": "http request",
        "z": "fa8c9e54db2d0f2a",
        "name": "Envoy-S Production/Inverter Request",
        "method": "GET",
        "ret": "obj",
        "paytoqs": "ignore",
        "url": "http://192.168.10.40/api/v1/production/inverters",
        "tls": "",
        "persist": false,
        "proxy": "",
        "insecureHTTPParser": false,
        "authType": "digest",
        "senderr": false,
        "headers": [],
        "credentials": {},
        "x": 750,
        "y": 300,
        "wires": [
            [
                "8bcd8e7e.695e68"
            ]
        ]
    },
    {
        "id": "8bcd8e7e.695e68",
        "type": "split",
        "z": "fa8c9e54db2d0f2a",
        "name": "",
        "splt": "\\n",
        "spltType": "str",
        "arraySplt": 1,
        "arraySpltType": "len",
        "stream": false,
        "addname": "",
        "x": 430,
        "y": 400,
        "wires": [
            [
                "86287b9b.69f7b8"
            ]
        ]
    },
    {
        "id": "86287b9b.69f7b8",
        "type": "function",
        "z": "fa8c9e54db2d0f2a",
        "name": "Solar Production Inverters to Domoticz",
        "func": "switch (msg.payload.serialNumber) {\n\n    case \"121851005629\": //Solar Panel 1\n    if ((msg.payload.lastReportWatts) < 0) (msg.payload.lastReportWatts) = 0;\n    msg.payload = {\"command\":\"udevice\",\"idx\":263,\"nvalue\":0,\"svalue\":((msg.payload.lastReportWatts).toString() + \";0\")};\n    break;\n\n    case \"121851003477\": //Solar Panel 2\n    if ((msg.payload.lastReportWatts) < 0) (msg.payload.lastReportWatts) = 0;\n    msg.payload = {\"command\":\"udevice\",\"idx\":264,\"nvalue\":0,\"svalue\":((msg.payload.lastReportWatts).toString() + \";0\")};\n    break;\n\n    case \"121834020289\": //Solar Panel 3\n    if ((msg.payload.lastReportWatts) < 0) (msg.payload.lastReportWatts) = 0;\n    msg.payload = {\"command\":\"udevice\",\"idx\":265,\"nvalue\":0,\"svalue\":((msg.payload.lastReportWatts).toString() + \";0\")};\n    break;\n\n    case \"121834020404\": //Solar Panel 4\n    if ((msg.payload.lastReportWatts) < 0) (msg.payload.lastReportWatts) = 0;\n    msg.payload = {\"command\":\"udevice\",\"idx\":266,\"nvalue\":0,\"svalue\":((msg.payload.lastReportWatts).toString() + \";0\")};\n    break;\n\n    case \"121834010561\": //Solar Panel 5\n    if ((msg.payload.lastReportWatts) < 0) (msg.payload.lastReportWatts) = 0;\n    msg.payload = {\"command\":\"udevice\",\"idx\":267,\"nvalue\":0,\"svalue\":((msg.payload.lastReportWatts).toString() + \";0\")};\n    break;\n\n    case \"121834019489\": //Solar Panel 6\n    if ((msg.payload.lastReportWatts) < 0) (msg.payload.lastReportWatts) = 0;\n    msg.payload = {\"command\":\"udevice\",\"idx\":268,\"nvalue\":0,\"svalue\":((msg.payload.lastReportWatts).toString() + \";0\")};\n    break;\n\n    case \"121851003159\": //Solar Panel 7\n    if ((msg.payload.lastReportWatts) < 0) (msg.payload.lastReportWatts) = 0;\n    msg.payload = {\"command\":\"udevice\",\"idx\":269,\"nvalue\":0,\"svalue\":((msg.payload.lastReportWatts).toString() + \";0\")};\n    break;\n\n    case \"121851009091\": //Solar Panel 8\n    if ((msg.payload.lastReportWatts) < 0) (msg.payload.lastReportWatts) = 0;\n    msg.payload = {\"command\":\"udevice\",\"idx\":270,\"nvalue\":0,\"svalue\":((msg.payload.lastReportWatts).toString() + \";0\")};\n    break;\n}\nreturn msg;\n",
        "outputs": 1,
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "libs": [],
        "x": 700,
        "y": 400,
        "wires": [
            [
                "ded33082d29e4182"
            ]
        ]
    },
    {
        "id": "df136f90.4190e",
        "type": "mqtt out",
        "z": "fa8c9e54db2d0f2a",
        "name": "Domoticz In",
        "topic": "domoticz/in",
        "qos": "0",
        "retain": "false",
        "respTopic": "",
        "contentType": "",
        "userProps": "",
        "correl": "",
        "expiry": "",
        "broker": "108bbff65a6cdbf3",
        "x": 990,
        "y": 460,
        "wires": []
    },
    {
        "id": "ded33082d29e4182",
        "type": "debug",
        "z": "fa8c9e54db2d0f2a",
        "name": "debug 3",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "false",
        "statusVal": "",
        "statusType": "auto",
        "x": 980,
        "y": 400,
        "wires": []
    },
    {
        "id": "108bbff65a6cdbf3",
        "type": "mqtt-broker",
        "name": "",
        "broker": "192.168.10.51",
        "port": "1883",
        "clientid": "",
        "autoConnect": true,
        "usetls": false,
        "protocolVersion": "4",
        "keepalive": "60",
        "cleansession": true,
        "birthTopic": "",
        "birthQos": "0",
        "birthPayload": "",
        "birthMsg": {},
        "closeTopic": "",
        "closeQos": "0",
        "closePayload": "",
        "closeMsg": {},
        "willTopic": "",
        "willQos": "0",
        "willPayload": "",
        "willMsg": {},
        "userProps": "",
        "sessionExpiry": ""
    }
]

Regards

[SumDum]

Thank you FireWizard. I think gizmocuz is onto it now over in github.

Thanks for the extra info above, I'll try that if I'm still having problems after tomorrow's build.

[FireWizard]

Hi @SumDum

I saw the discussion and outcome of it on Github.
So, if the result of tomorrows release satisfies you, we close this discussion.

There is one thing that is worrying me a little, in what @gizmocuz is saying:

What I can do is use the last digits of the serials as the ID, the first seems to be fixed

How far is it fixed.

If I look to your serials, I see that all your serial numbers are starting with 122 and the remaining 9 numbers are variable, while my serials are starting with 121 and the remaining 9 are variable.
My panels/inverters are from 2019 and yours are a little bit younger (2020, 2021 and 2022)

We might expect that in the future the serial numbers will go up and then we will see serials starting with 124 or 125.
How are the serials of the new IQ8 inverter?

I would take the complete serial as the ID and not the last digits (how many?) of it.

What is your opinion?

Regards

[TurboX]

Hello,

I use the enphase pluging (domoticz beto 14928 docker), it works but the production (in watt) is not refreshed as it sould. It is more 5min than 30sec, the consumption is refreshed every 30s has requested into the plugin parameters.
In parallele I use Home Assistant with enphase add-on and I have a production refresh every 60s. Do you observe the same behavior?

[gizmocuz]

In the recent beta the complete serial number of each inverter is used as ID.
So, there can be no mismatch.
The issue above was that there where inverters replaced causing a shift

@TurboX, No idea, please use the native Enphase hardware inside Domoticz now. There is no reason for an external plugin

[TurboX]

Hello Gizmocuz,

I use the native Enphase hardware, I have updated my docker to 15071 (with inverter recreated) but I observe the same refreshing behavior. If you set the refresh rate to 30s, your current production in watt are refreshed every 30s?

[Xavier82]

Hi all,

So I upgraded to 2023.1 version.
I have Enphase Solarpower system, version D7.0.88
I want to use the Enphase Envoy with LAN interface feature.
I filled in the Ip-address + port (80) And username and password.
Then I get the next error logs:
2023-02-15 09:13:54.218 Status: Enphase Envoy: Connected, serial: XXXXXXX, software: D7.0.88
2023-02-15 09:13:54.861 Error: Enphase Envoy: Invalid data received! (no session_id)
2023-02-15 09:13:55.190 Error: Enphase Envoy: Invalid data received! (inverter details)

When using the feature of https://github.com/H4nsie/EnphaseEnvoy I don't have this issue, using the same credentials.
Based on the error log it doesn't seem to be an issue with the credentials since it says "connected".

I use the Enphase Envoy-S Metered with fixed IP-address.
Also good to mention I think is that when going to the ip-address of the Enphase Envoy-S Metered I first need to go https://entrez.enphaseenergy.com/entrez_tokens to get a token which I need to enter before I can get in the Envoy-S.
Logging in to https://entrez.enphaseenergy.com/entrez_tokens needs username/e-mail + password.

BTW: I didn't got this to work neither on the 2022.2 version.....

Anyone else with this issue?

[Xavier82]

So even after reading https://www.domoticz.com/wiki/Enphase and adding the token to the user variable I still get the same error:
2023-02-15 20:07:30.260 Error: Enphase Envoy: Invalid data received! (no session_id)
2023-02-15 20:07:30.598 Error: Enphase Envoy: Invalid data received! (inverter details)

Am I doing something wrong?

[brugje]

I also have the same problem
Enphase is recognized by id nr and software version but i can't get data into domoticz

[brugje]

When i do a curl on my envoy Ip i get.
Is there somebody with a solution.
groet Jan

[rrozema]

Hi, I just noticed that my enphase panels no longer pass their information into Domoticz after I upgraded to 2023.1. All enphase devices are shown in Domoticz with red title bars and show no more updates since the update.

Devices not getting any more updates

Capture1.JPG (20.94 KiB) Viewed 18413 times

I have the Domoticz standard hardware for installed:

Enphase hardware

Capture2.JPG (65.78 KiB) Viewed 18413 times

The http://192.168.128.103 address is showing me the enphase envoy screen in a browser correctly.

When I look into the Domoticz log though I find below messages just after I activated the 'enphase' hardware. Other than that I see no messages from enphase, even with full logging enabled.

Code: Select all

2023-02-27 11:53:47.146 Status: enphase: Worker started...
2023-02-27 11:53:51.262 Status: enphase: Connected, serial: 121831009724, software: R5.0.55
2023-02-27 11:53:51.262 Status: enphase: Unsupported software version! Please contact us for support!
2023-02-27 11:53:52.717 enphase: General/kWh (Zonnepanelen Productie)
2023-02-27 11:53:52.740 enphase: General/kWh (Enphase kWh Consumption)
2023-02-27 11:53:52.837 enphase: General/kWh (Enphase kWh Net Consumption)

What could be the issue, and of course: how do i get to work again? This integration has worked like a charm since at least 2019. Please help!

log

Capture3.JPG (53.52 KiB) Viewed 18413 times