I think you have it a bit backwards. The owner is the one with read-only access; it’s the installer and/or maintainer who can control the system.
Did you try the app with that “self-installer owner account”? Did it give you control access?
If not, how exactly are you getting the authentication token from enphase (entrez) to make the api calls to disable/enable the power production?
If my app isn’t giving you control access, but you use the same credentials to do your own api calls to control production, then you might hold the missing piece of puzzle
I do have 2 accounts. First had my own owner account, but wanted to have access to the control settings as well. So as by the Reddit suggestions, I did do all the Enphase university courses and contacted Enphase to give me the self installer access so I could use enlighten manager. However, they won’t provide you anymore because nowadays you can buy it for €300.
After a lot of back and forth, they came with the solution to let me create a new self installer account. Normally you can’t assign a self installer account as a new installer nor maintainer when a site is installed by a company. But Enphase can. The assigned me to my site but then I had read-only access only. After contacting them again, they told me that they would assign my self-installer account whit owner access to the site, after which I finally had all the control rights. All of this very recently
I did use my self-installer account to sign in to your app, but it tells me i don’t have controll access. For my own usage I do generate the entrez token on my self installer account, as my original account doesn’t give me the wanted rights. I am more than happy to debug some things for you, just tell me what you need!
Not sure if you already checked it, but the HA integration decodes the entrez JWT token to determines the access level. Just checked my own tokens with cyberchef:
This is literally what i’m looking for when pairing the device (“installer” or “maintainer”). If the app says you don’t have controller access, then this is not what the app got back when getting the token.
I guess so. Tested your API endpoint, and my token appeared as a owner instead of installer indeed. Not sure, maybe there is an undocumented parameter that can be set for the API endpoint to switch to an installer account, but that’s just guessing.
When switching off, does it impact Enphase batteries?
While I am really grateful and happy with this app, it does not fully address the topic of this thread, since Enphase system can still export energy from the batteries if the prices are negative. My intent to mention this is just to share a thought if you intent to work out this app to support Enphase batteries as well.
Thats weird. I’m just showing what the Envoy is reporting. But it might be a good idea to clamp this value to 0 indeed.
Yes, this can have multiple causes. All of them (that i know of) are addressed in the next version. Amongst others, I’m going to drop support for the “envoy.local” hostname, as its not reliable.
We’re not controlling batteries, but the batteries will react to the situation of course, depending on their settings.
Yes I intent to add support for other Enphase products (batteries & charger), but I’m focusing on the PV system first for now.
Without sunlight, the inverters and the IQ gateway are in a sort of standby mode and consume a small amount of energy: approximately 10 watts (the number of inverters affects this value).
Rrrrrrrrrrrrright… @Timelezz must have the Metered gateway that’s measuring the actual production/usage. With me --having unmetered-- it’s just showing what the gateway itself is reporting: 0 at night.
But like i said, i’ll clamp it a minimum of 0 to prevent unwanted readouts.
Great app development—everything looks very promising, especially the integrations.
However, I only have an installer account (with access to multiple systems witch i installed), and I am currently unable to control the inverters at my own home. I receive a message stating that I am not an installer.
If I can assist with debugging or testing in any way, please let me know!
This is fixed for a number of situations in the new version that is now on the public test branch (1.2.1).
Please try the test version and let me know if it works for you!