Enphase Envoy not fetching all sites in account resulting in partial info #117282
Comments
|
Hey there @bdraco, @cgarwood, @dgomes, @joostlek, @catsmanac, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) enphase_envoy documentation |
|
Hi @jmwhite5, so same username/password and 2 site-id? And each site has an Envoy? And only 1 Envoy works in HA? Currently we are not aware how to specify a site-id in the protocol to obtain the token. It's not described in the Enphase document that describes how to get a token programmatically. Won't mean it can't be done, just that we don't know how yet. Is splitting in 2 username/password sets, one for each site-id is an workaround as Enlighten isn't providing overall values anyway? |
|
Yes. 2 site IDs for 1 username/password.
Each site has its own envoy. I am currently only getting data from my 2024 system. My 2015 system used to work, but now I don’t get info from it.
Looking at the APIv2, it looks like the <https://developer.enphase.com/docs#index>systems <https://developer.enphase.com/docs#api-systems> call returns the list of sites. (Looks like APIv4 is now available, which also includes this info).
Sample request
GET https://api.enphaseenergy.com/api/v2/systems
Sample response
{
"systems": [
{
"system_id": 67,
"system_name": "Sample Residence 1",
"system_public_name": "Sample Residence 1",
"status": "normal",
"timezone": "America/Los_Angeles",
"country": "US",
"state": "CA",
"city": "Sebastopol",
"postal_code": "95472",
"connection_type": "ethernet",
"meta": {"status": "normal", "last_report_at": 1445619615, "last_energy_at": 1445619033, "operational_at": 1357023600}
},
{
"system_id": 72,
"system_name": "Sample Residence 2",
"system_public_name": "Sample Residence 2",
"status": "normal",
"timezone": "America/Los_Angeles",
"country": "US",
"state": "CA",
"city": "Placerville",
"postal_code": "95667",
"connection_type": "ethernet",
"meta": {"status": "comm", "last_report_at": 1449959488, "last_energy_at": 1449945104, "operational_at": 1418912581}
}
],
"next": "4e7a453d0a"
}
And yes, I would be happy splitting my system into 2 using the truple userid/password/systemID. Whatever works for you.
… On May 12, 2024, at 01:48, Arie Catsman ***@***.***> wrote:
Hi @jmwhite5 <https://github.com/jmwhite5>, so same username/password and 2 site-id? And each site has an Envoy? And only 1 Envoy works in HA?
Currently we are not aware how to specify a site-id in the protocol to obtain the token. It's not described in the Enphase document that describes ho to get a token programmatically. Won't mean it can't be done, just that we don't know how yet.
Is splitting in 2 username/password sets, one for each site-id is an workaround as Enlighten isn't providing overall values anyway?
—
Reply to this email directly, view it on GitHub <#117282 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJOAMXM3XZAELSH47VR7GLZB4UGBAVCNFSM6AAAAABHSMTE6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGE3TANBSGY>.
You are receiving this because you were mentioned.
|
|
So in HA you had the 2015 Envoy configured and working. Then you added the 2024 on with its own IP, using same username and password also used for the 2015 one. But the new one is not showing data in HA. Is there any errors in the log file? Does the second Envoy get initialized or does it just keeps on trying? Can you enable debug on the 2024 Envoy or does the debug option not yet show? Are both envoy showing information and a
We're not using that API V2 or V4 as that is the Enlighten Cloud API. What we're using is the Enlighten login as described in IQ Gateway Local API or UI Access using Token-TEB-00060.1.0-EN-2023-08-14.pdf and it has no description of specifying site id. This can mean 2 things, it's needed and not documented, or username and envoy serial number is sufficient for it. If both Envoy have a If you can't enable debug on the 2024 Envoy, add below to the configuration.yaml file: logger:
default: warning
logs:
homeassistant.components.enphase_envoy: debug
pyenphase: debug
httpx: debug
httpcore: debugand restart HA. Let it run for some time to see if it reports on the 2024 Envoy an d if so upload the log file here. And remove the setting from the configuration file again followed by HA restart. |
|
When you wrote “with its own IP” (and in previous email you said “local API”), it made me realize that Home Assistant was talking directly to each envoy device and not the cloud. I forget exactly what I did when I added the new system, but clearly, I was confused.
This is how I fixed things:
1) I reconfigured both envoys to use static IP addresses with different hostnames.
2) I re-did my config from scratch and was able to add both systems (old and new) using their DIFFERENT IP addresses and everything now seems to be working correctly.
Home Assistant is actually better than Enphase’s web site because I get both envoy’s data to merge properly into the Energy panel and don’t have to switch between “sites”. So thank you for your help and for writing this integration!
… On May 12, 2024, at 13:27, Arie Catsman ***@***.***> wrote:
So in HA you had the 2015 Envoy configured and working. Then you added the 2024 on with its own IP, using same username and password also used for the 2015 one.
But the new one is not showing data in HA. Is there any errors in the log file? Does the second Envoy get initialized or does it just keeps on trying? Can you enable debug <https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging> on the 2024 Envoy or does the debug option not yet show? Are both envoy showing information and a download diagnostic button?
afbeelding.png (view on web) <https://github.com/home-assistant/core/assets/120491684/933d4adf-24fb-4221-be93-780fb010635b>
We're not using that API V2 or V4 as that is the Enlighten Cloud API. What we're using is the Enlighten login as described in IQ Gateway Local API or UI Access using Token-TEB-00060.1.0-EN-2023-08-14.pdf <https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication> and it has no description of specifying site id.
This can mean 2 things, it's needed and not documented, or username and envoy serial number is sufficient for it.
If both Envoy have a download diagnostic button then can you post the files that download when using the button here?
If you can't enable debug on the 2024 Envoy, add below to the configuration.yaml file:
logger:
default: warning
logs:
homeassistant.components.enphase_envoy: debug
pyenphase: debug
httpx: debug
httpcore: debug
and restart HA. Let it run for some time to see if it reports on the 2024 Envoy an d if so upload the log file here. And remove the setting from the configuration file again followed by HA restart.
—
Reply to this email directly, view it on GitHub <#117282 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJOAMUQJZSN32RAJQQSJ7TZB7GE5AVCNFSM6AAAAABHSMTE6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGM3DKNRWGU>.
You are receiving this because you were mentioned.
|
|
The current implementation works for my scenario. No additional work required. |
The problem
I added new solar panels this year and Enphase created a separate "Site" because they cannot merge the older solar panel inverters with the new ones. So when the Home Assistant Enphase integration logs into my account without specifying which "Site", it defaults to the oldest site and doesn't retrieve all the inverters. Could the integration either fetch ALL the Sites by default (would not impact most users but would benefit users like me) ? Alternatively, allow user to specify which site to fetch and I could add 2 Enphase instances.
What version of Home Assistant Core has the issue?
core-2024.5.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Enphase Envoy
Link to integration documentation on our website
https://www.home-assistant.io/integrations/enphase_envoy/
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: