Enphase envoy not showing certain entity values anymore after enphase updated the unit om 1-4-2024

[Rotil66]

The problem

After enphase did a overnight update on 01-04-2024. The problem started that I had to reauthorize the intergration. (never needed that before) after doing this the intergration was working again but some of the (automatically) found entity's are not showing values. The lifetime production, dayly production, 7 day's production. are not showing a value. The current production is showing a value but I can't select this in the standard energie layout. (it's needed for this layout to work) I my own layout I can show this current production entity. Since I don't have a deep knowledge of HA Indon't know how to solve this. The integration has run for years flawlessly. It already stopped working justbefore the last update of roday to 24.4.0 (?) The problemz started right after the update from enphase ot self on 01-04-2024. (they told me the did an overnight update)

What version of Home Assistant Core has the issue?

All after the envoy it self was updated by enphase

What was the last working version of Home Assistant Core?

The one before 2024-4-0 Was working but stopped.

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Enphase envoy (dev)

Link to integration documentation on our website

No response

Diagnostics information

Sorry I'm not able to paste the log text with my phone. Has to try later on my laptop

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Sorry that I'm not very familiar with reporting a problem. So please let me know how I can provide needed information.

Thanks , Rolof

[home-assistant[bot]]

Hey there @bdraco, @cgarwood, @dgomes, @joostlek, @catsmanac, mind taking a look at this issue as it has been labeled with an integration (enphase_envoy) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `enphase_envoy` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign enphase_envoy` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

enphase_envoy documentation enphase_envoy source _{^{(message by IssueLinks)}}

[tierrie]

Enphase recently changed the way they handled authentication. I had to make changes to my Enphase integration mid-March due to my token expiration. Your update may have caused the same issue: https://support.enphase.com/s/question/0D5Ps000008MicjKAC/how-can-i-get-a-token-needed-for-home-assistant

Instructions on how to get a token: https://enphase.com/download/accessing-iq-gateway-local-apis-or-local-ui-token-based-authentication?_ga=2.207755409.223774952.1678687434-1765750934.1676903595

[cgarwood]

If you're actually using "Enphase Envoy (dev)" that's a custom component and you'll need to log the issue in that components repository. The standard Enphase Envoy integration in HA handles token authentication automatically now, I'd suggest using the standard integration instead of the custom one at this point.

[Rotil66]

Hi Charles,

Before I used the standard intergration I only changed it after it was failing in the same way and got the advice to try this. Now I have to see how to get it out, is on reistall it now find this (dev) version.

⁣BlueMail voor Android downloaden ​

Op 5 apr 2024 04:16, om 04:16, Charles Garwood @.***> schreef:

If you're actually using "Enphase Envoy (dev)" that's a custom component and you'll need to log the issue in that components repository. The standard Enphase Envoy integration in HA handles token authentication automatically now, I'd suggest using the standard integration instead of the custom one at this point.

-- Reply to this email directly or view it on GitHub: https://github.com/home-assistant/core/issues/114901#issuecomment-2038637072 You are receiving this because you authored the thread.

Message ID: @.***>

[catsmanac]

Hi @Rotil66, assuming you switched back to the core integration, can you share the diagnostics report of the envoy here?

In HA: Settings / Devices & Services / Click on the Enphase Envoy / Click on .. devices / In the List click on Envoy <serialno> at the top of the list / Click on Download Diagnostics.

The diagnostic file will download to your device. In your reply use the to share the file as file.

[pollev]

I am experiencing the same issue. I was originally using the DEV version as well and have now switched back to the core version. I am prompted to re-configure the integration. When doing so I am given this error:

Invalid authentication: Unable to obtain token for Envoy authentication from https://entrez.enphaseenergy.com/tokens: 500: {"timestamp":1712315554669,"message":"Failure in loading token configuration for <my email here> and 122242016316 envoy"}

Could I supply you with any other information to help troubleshoot? I assume this information is also relevant for you:

[catsmanac]

Hi @pollev, so previously with the dev version you also used the token from enphase? Or did your envoy just upgrade and now need to start uses the tokens?

[pollev]

Hi,

The dev version was also using the token and failing also on token aquisition. I had the same experience as @Rotil66. My sensors went to unavailable. The error message in the logs was identical at that point to the error message I poster earlier that I receive now when re-configuring the integration.

[catsmanac]

When checking: https://enlighten.enphaseenergy.com/login

I'm getting:

So it seems the Enphase server is overloaded. There's more reports of this earlier this week. There also question with Enphase with the same error both of you are reporting: https://support.enphase.com/s/question/0D5Ps00000EY5AuKAL/how-to-get-token-from-envoysmetereu-with-the-following-error-message-send-by-enphase

You can try that link later and login there and manually get a token to check if all is working again. Once all is working again the Envoy may be able to get going again in Home Assistant.

[pollev]

Hi, I'm still experiencing the same issue. I have tried at various times during the day to connect so it doesn't seem like a load problem. When going to the link you provided, I can simply log in with my credentials with no issue. But the problem persists when using the integration.

In fact, if I go to 'https://entrez.enphaseenergy.com/entrez_tokens' and try to create a token there I get an error as well:

[pollev]

Update: I had a call with the enphase envoy support team. I explained my issue as described here. They updated something on their end (I don't know what exactly) and afterwards I was able to create access tokens again.

So for anyone struggling with the same issue, I would recommend verifying if you are able to create an access token on https://entrez.enphaseenergy.com/entrez_tokens and contact their support if you can not.

[catsmanac]

Thanks for sharing that experience @pollev.

@Rotil66, if you still have the issue you may want to try the same.

[catsmanac]

@home-assistant close