Any Interest In Collaborating On Extending To "New" Enphase Local APIs?

[jbnance]

Hello Alex,

I love this project. The work you have done here is fantastic. I'm wondering if you have any interest in working together to include some of the other data outlined in the newer(?) APIs:

https://enphase.com/download/iq-gateway-access-using-local-apis-or-local-ui-token-based-authentication-tech-brief

You're already pulling from at least one of them (inverter_production_data: /api/v1/production/inverters). I'm hoping to get some battery data into the mix. I'm also not sure how much longer the production.json endpoint is going to be available. It seems that Enphase is making some... interesting... changes:

https://support.enphase.com/s/question/0D53m00006ySLuRCAW/unimpressed-with-loss-of-local-api-connectivity-to-envoys

...which I'm sure has nothing to do with: https://developer-v4.enphase.com/developer-plans

:-)

Either way, I appreciate what you've done thus far.

[amykyta3]

Nice. I was not aware of some of those other JSON API paths. I'll see if it makes sense to pull from the other ones instead of production.json.

On my personal setup, I have the envoy locked away behind a VLAN to prevent it from being able to get firmware updates or access the internet whatsoever. For the reasons you mentioned, I dont trust enphase to preserve the existing API. Even now, the token authentication they use is absolutely idiotic.

Those developer plans are surely not a good sign either. Yikes.

[jbnance]

I uploaded the script I wrote to dump data for inspection as well as some example output: https://github.com/jbnance/enphase-misc

Let me know how I can help. I'm going to try and compare some of the data during daylight hours and also when I'm drawing from battery to see if I can start modeling out what these fields mean.