|
|
|
|
|
|
by matthew1471
876 days ago
|
|
|
Thanks for the shoutout to my wrapper and docs too :) My GitHub repo serves 2 purposes: 1. To provide a reusable wrapper (currently only Python, https://github.com/Matthew1471/Enphase-API/blob/main/Documen...) to talk to the LAN API, it's even installable via pip. 2. To document what the LAN API returns and all the URL endpoints (https://github.com/Matthew1471/Enphase-API/tree/main/Documen...). I would like to see more people using the wrapper so we have a common way of talking to the IQ Gateway (there's a lot of tightly coupled projects on GitHub), but most people seem more interested in the docs I provide and rolling their own wrapper. I always have plans to add more to it - I found multiple security vulnerabilities in the IQ Gateway and that allowed me to get a dump of the firmware - so there's plenty more URLs for me to write about :) |
|
|
Great that you're able to update settings... not just read data. I assume that changes to settings are synced with Enphase's cloud as if done with the cloud-based API.
I assume it's not possible or advisable to disconnect from Enphase's cloud altogether (please let me know if that's actually no big deal). [EDIT: Thanks for addressing this in your other comment.]
Enphase released a better EV charger* a few months ago, that's integrated with the other IQ stuff. It can dynamically send excess solar production into the EV instead of exporting to the grid (and can be set to top off the EV battery with grid imports in the middle of the night). I'll finish installing mine this week. ...Please consider incorporating that into your wrapper :)
I too am pretty quick to roll my own stuff. But I'll try to practice restraint, and leverage your wrapper (and treat it as a standard).
* https://enphase.com/store/ev-chargers/connected-ev-chargers-...