Domoticz

vwstepha wrote: ↑Monday 02 January 2023 20:15 Good evening everyone! Best wishes for this New Year!!!!

I want to monitor my Enphase meter
I put the script available on the 1st page (thanks to the author!!) in the events
I created a Dummy and the idx 16 was assigned by Dz.
in the settings, there is the authorization to create new sensors.

Code: Select all

-- ==============================
        -- Your setting here
        -- ==============================
        -- Change to reflect location of your wget and remove -- ( comment ) in front of the declaration for your OS  
        -- wgetExecutable = '/usr/bin/wget'                 -- Linux
        -- wgetExecutable = 'c:\\"Program files"\\wget.exe' -- Windows: double back slashes where one is in the path

                local Enphase =    {
                                ip = '192.168.1.195',         -- IP address of your local enphase hub
                                password = 'ac6k4732',            -- Change to your calculated password. See description above on how to get this.

                                dummyHardwareIDX = 16,               -- Change to ID of your virtual hardware
                                useProduction = true,
                                productionDeviceName = 'l***l',
                                useInverters = true,
                                inverterDevicePrefix = 'micro inverter: ',  -- script use this prefix + serial number of inverter.
                                createDevices = true,              -- Should the script create devices if they are not defined yet.

                                -- please note that the counter display will only show a rough estimate
                                -- of the produced energy over the period the device lives in domoticz and the script is active.

        -- =========================================
        -- == No changes required below this line ==
        -- ==========================================
                                user = 'installer',                                     -- I think this is a fixed username
                                inverterDeviceType = 'Electric (instant+Counter)',      -- script use this type for inverters
                                productionDeviceType = 'Electric (instant+Counter)',    -- script use this type for total production
                                productionAPI = '/api/v1/production',
                                invertersAPI = '/api/v1/production/inverters',

                            }

I filled in my personal info except "micro inverter". I did not understand what I should put?
Do I have to put the serial number of the Micro inverter and therefore create as many scripts as there are micro inverters?
Can you help me?
Thank you

vwstepha wrote: ↑Monday 02 January 2023 20:41 Thank you for your reply
I authorized the creation



So I'm going to wait quietly tomorrow morning because, if I understood correctly, it will start when the micro Inverters produce electricity
Thanks again!

{
  "wattHoursToday": 2,
  "wattHoursSevenDays": 16490,
  "wattHoursLifetime": 6170377,
  "wattsNow": 36
}

[
  {
    "serialNumber": "482*********",
    "lastReportDate": 1672733665,
    "devType": 1,
    "lastReportWatts": 0,
    "maxReportWatts": 260
  },
  {
    "serialNumber": "482*********",
    "lastReportDate": 1672733671,
    "devType": 1,
    "lastReportWatts": 1,
    "maxReportWatts": 149
  },
  {
    "serialNumber": "482*********",
    "lastReportDate": 1672733660,
    "devType": 1,
    "lastReportWatts": 1,
    "maxReportWatts": 149
  }
  ..... etc ...

vwstepha wrote: ↑Tuesday 03 January 2023 8:27 Hi.
I found this morning with an error

Code: Select all

2023-01-03 08:51:00.504 Status: dzVents: Info: Enphase_0.201910122300: ------ Start internal script: Enphase:, trigger: "every 1 minutes between sunrise and 45 minutes after sunset"
2023-01-03 08:51:00.505 Status: dzVents: Info: Enphase_0.201910122300: /usr/bin/wget -T 3 --user installer --password ac6***** -O - 192.168.1.195/api/v1/production
2023-01-03 08:51:00.878 Status: dzVents: Info: Enphase_0.201910122300: ------ Finished Enphase
2023-01-03 08:51:00.877 Error: dzVents: Error: (3.1.8) Enphase_0.201910122300: ReturnCode: 5
2023-01-03 08:51:00.877 commandOutput:
2023-01-03 08:51:00.877
2023-01-03 08:51:00.877 Error: dzVents: Error: (3.1.8) Enphase_0.201910122300: ReturnCode: 5
2023-01-03 08:51:00.877 commandOutput:
2023-01-03 08:51:00.877
2023-01-03 08:51:00.878 Error: dzVents: Error: (3.1.8) Enphase_0.201910122300: An error occurred when calling event handler Enphase
2023-01-03 08:51:00.878 Error: dzVents: Error: (3.1.8) Enphase_0.201910122300: ...i/domoticz/scripts/dzVents/generated_scripts/Enphase.lua:177: attempt to index a nil value (local 'productionTable')

I don't know what to change or check....
Thank you for your help!

/usr/bin/wget -T 3 --user installer --password ac6***** -O - 192.168.1.195/api/v1/production

vwstepha wrote: ↑Tuesday 03 January 2023 9:31 hi
Your links is ok

Code: Select all

{
  "wattHoursToday": 109,
  "wattHoursSevenDays": 37273,
  "wattHoursLifetime": 114956,
  "wattsNow": 473
}

Code: Select all

[
  {
    "serialNumber": "4822400",
    "lastReportDate": 1672733836,
    "devType": 1,
    "lastReportWatts": 45,
    "maxReportWatts": 224
  },
  {
    "serialNumber": "482240",
    "lastReportDate": 1672733837,
    "devType": 1,
    "lastReportWatts": 45,
    "maxReportWatts": 219
  },
  {
    "serialNumber": "482240",
    "lastReportDate": 1672733838,
    "devType": 1,
    "lastReportWatts": 17,
    "maxReportWatts": 139
  },
  {
    "serialNumber": "482240",
    "lastReportDate": 1672733842,
    "devType": 1,
    "lastReportWatts": 60,
    "maxReportWatts": 181

in the script I put the code found thanks to the apk: AC6*****
and the user is 'installer'

/usr/bin/wget -T 3 --user installer --password ac6***** --no-check-certificate -O - 192.168.1.195/api/v1/production

Software Version
D5.0.55 (4f2662)
Software Build Date
10 Dec, 2020 10:15 AM

vwstepha wrote: ↑Tuesday 03 January 2023 10:08 thank you for your help
this time the result is not good

Code: Select all

--2023-01-03 10:05:00--  http://192.168.1.195/api/v1/production
Connecting to 192.168.1.195:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://192.168.1.195/api/v1/production [following]
--2023-01-03 10:05:00--  https://192.168.1.195/api/v1/production
Connecting to 192.168.1.195:443... connected.
ERROR: The certificate of ‘192.168.1.195’ is not trusted.
ERROR: The certificate of ‘192.168.1.195’ doesn't have a known issuer.

vwstepha wrote: ↑Tuesday 03 January 2023 10:57 indeed "http://192.168.1.195/api/v1/production" also redirects to insecure https....

here is the response with --no-check-certificate

Code: Select all

--2023-01-03 10:50:14--  http://192.168.1.195/api/v1/production
Connecting to 192.168.1.195:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://192.168.1.195/api/v1/production [following]
--2023-01-03 10:50:14--  https://192.168.1.195/api/v1/production
Connecting to 192.168.1.195:443... connected.
WARNING: The certificate of ‘192.168.1.195’ is not trusted.
WARNING: The certificate of ‘192.168.1.195’ doesn't have a known issuer.
The certificate's owner does not match hostname ‘192.168.1.195’
HTTP request sent, awaiting response... 401 Unauthorized
Unknown authentication scheme.

Username/Password Authentication Failed.

You are totally right. My software version is newer

Code: Select all

Version logicielle
D7.0.88 (5580b1)
Date de version logicielle
18 jan, 2022 5:42 Matin

my installation is very recent (December 2022!)

So I don't know what to do....
thank you for your help

vwstepha wrote: ↑Tuesday 03 January 2023 11:40 I read the pdf and tried to understand.
I have created a token which has a validity of one year.
I stored it in a text file.
access via the token works on the web browser.
I tested with Putty on the raspberry

Code: Select all

curl -f -k -H 'Accept: application/json' -H 'Authorization: Bearer eyJraWQiOiI3ZDEwMDA1ZC03O****    ********’ -X GET https://192.168.1.195/api/v1/production/inverters

no answer from rapsberry....

Code: Select all

pi@raspberrypi:~ $ curl -f -k -H 'Accept: application/json' -H 'Authorization: Bearer eyJraWQiOiI3ZDEwMDA1ZC03ODk5LTRkMG*** *** xWw’ -X GET https://192.168.1.195/api/v1/production/inverters
>
>
>
> ^C

i click on CTRL+C to break
No answeer but no error....

FireWizard wrote: ↑Tuesday 03 January 2023 12:46 Hi,

Why not use the latest beta release?
It is natevely supported from version 14768.

Regards

With the native plugin you can read power usage etc but not all the inverters separately

If you are not using IQ8+ inverters the main version remains D5.0.62 instead of v7.x version. That’s why my envoy is still version 5.x.xx.

FireWizard wrote: ↑Tuesday 03 January 2023 14:23 Hello @SanderRoelofs,

You wrote:

With the native plugin you can read power usage etc but not all the inverters separately

This is not true anymore. The Enphase "hardware" has been updated with individual read-out of the inverters and it supports now both system firmware D5 and D7


Screenshot_Enphase_Config.png


See also: https://github.com/domoticz/domoticz/issues/5377

This is something you might want to read as well, in order to get updated.

If you are not using IQ8+ inverters the main version remains D5.0.62 instead of v7.x version. That’s why my envoy is still version 5.x.xx.

This isn't true either. Of course, if you install the brand new IQ8+ inverter, you need D7 but in that case you also have to use a new Enphase Gateway (the new name for Envoy). Unfortunately Enphase Envoy-S (Standard or metered) cannot be used with the new IQ8 series of microinverters.
But your existing Enphase Envoy-S may receive an update from version D5 to D7. Be aware of that, if someday the communication with your Envoy fails.

Also my Envoy is still on D5, but I'm prepared if an update is pushed.

I hope, I have updated you a liitle.

Regards