danielpatenaude / python_enlighten_api Goto Github PK

Hi Daniel,

If you make an error when connecting to enphase, the error is not displayed/logged right.

This line:

Maybe just replace dl.error with print ?

Jacco

I am sorry to bother you but I am having issue adding my information to the configs section. Below I am going to give you an example of how I have mine setup. The error I am getting is, name: 'adam' is not defined

"name": adam,
"user_id": [email protected],
"site_id": 2265555,
"api_url": api.enphaseenergy.com/api/v2/systems,
"api_key": c98a101222ff3487958ce5555555555,
"spreadsheet_id": [email protected]

Any advise you have would be great.

Thanks

I was experimenting with this project and encountered the same issue called out in the README:
"It appears there's a new v4 route (/api/v4/systems/{System_id}/devices/micros/{serial_no}/telemetry) that can get microinverter data based on a date range. This seems the more ideal way to get daily inverter data than my current way of having to get the current lifetime data minus the stored value. But unfortunately I have not been able to successfully call this route using the Enlighten API v4 docs. So maybe this route doesn't do what I think it does, and their docs don't make it very clear what it does. I always get a 401 - Not Authorized. If someone is able to get that figured out, please feel free to let me know."

I believe the issue (at least for me) stems from the free developer "Watt" plan which does not include device level monitoring. This is only included with the paid plans:

Unrelated, a few typos in the README:
"The Enphase API lacks the granulatiry granularity of seeing per inveter inverter daily stats."

Thank you for sharing this project.

Hi Daniel,

thanks for this repo. It's quite frustrating that enphase does not allow requesting on microinverter-level for subscription-plan watt. The enphase system (26 panels/inverters) will get installed in the next months, so I started to prepare some monitoring for the system including forecasting.

Have you ever tried the api: "/api/v4/systems/{system_id}/telemetry/production_micro" ? And what kind of data will you get?

Additional question: In which region/area is your system installed? Is 26,1 kW on 07.02.2022 the real production over all modules?

Thanks in advance.
olikr

v2 API will be retired Jan 18, 2023. Need to have this ported to the v4 version before then.

Hello

I'm hoping to use your code as a base for a personal project (using an inkplate as a solar usage display) and wanted to verify what license you would like me to treat at is MIT/GPL/etc?

Thanks

Hallo Daniel,

I made kind of same system for accessing enlighten api v4.

It is possible to renew the initial authorization of the app (get new acccess /refresh token). I contacted enlighten support about why this was needed: got no response. It is clear that enlighten api is developed for apps that regurly access enlighten api....

I made a selenium script to login into enlighten and permit app access and get new access token. I was not clever enough to do this in a straight forward way. Should however be possible with some authorization magic (cookies).
I needed to add timestamp book keeping of access/refresh tokens to create new access token when refresh token is expired.

I doubt if my selenium method should be published. What is your opinion about trying to develop a script that uses user credentials to create new access token using some advanced authorization script?

Groeten,
Ronald