-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
My Enphase integration has been unavailable for a few days #95851
Comments
Hey there @gtdiehl, 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 |
Please enable debug logging for the integration and add some logs. |
Your homeassistant install itself should have logs from the integration install failing: https://your.home:8123/config/logs If there is nothing in there related to enphase, check out https://www.home-assistant.io/integrations/system_log/ how to increase system logging. Increasing logging will usually slow down your system, so dont start logging everything you can think of :) |
I found this: Détails du journal (ERREUR) Unexpected exception |
And this : 2023-07-03 21:13:02.878 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Envoy 122240002467' for enphase_envoy integration not ready yet: Error communicating with API: ; Retrying in background |
Are you sure it has nothing to do with the firmware update from enphase? See this issue. I have the same issue, and that is the problem here. |
Seems to be related to gateway upgrade from enphase. D7.6.175 (f79c8d) |
I'm having the same issue, same firmware version. Stopped working since yesterday. |
same firmware version : D7.6.175 |
Hi, Same issues here with firmware version : D7.6.175 |
There is a new API V4 (instead of V2) and this new API request OAUTH : Note: Both Monitoring and Commissioning API follow OAuth 2.0 authentication. Each API request should include an OAuth 2.0 access token as Authorization header using the Bearer scheme, and the request should also include the API key of your application in header with name 'key'. |
Yes, it proposes to create a token but if you go to the website it's not actually possible: the gateway remains empty and there's no indication of what the service is. |
I have the same issue, since this morning it stopped in my home assistant. |
I will try this reposite in HACS |
Hello everyone, Incredible bad work on the part of enphase. I don't know if anyone from that company is here or is reading these lines... but it's obviously the last time I use a product from their brand. Its device management policy is disastrous, and this is already the last straw. They have introduced the need for a token for the use of their API . Aditionally I lost the access via the web (local IP). The token can be generate at: https://entrez.enphaseenergy.com/entrez_tokens The login credentials are the ones you use to access: enlighten.enphaseenergy.com Once logged in, you will need the name of the installation that is taken from: Menu: System My installation is not in English, so it may not exactly correspond to those titles. If the name is correct, you can now use the dropdown to choose your device and the token is generated. Copy it to a safe place. You have all the info at: I guess the integration will have to be adapted to support the new token. Regards, |
@shvirik I posted a comment on this topic https://support.enphase.com/s/question/0D53m00006ySLuRCAW/unimpressed-with-loss-of-local-api-connectivity-to-envoys. To all: feel free to leave a comment as well and to contact the support. They should know this is not something customer appreciate. Regards |
Thanks for the information, I have some questions, If you can answer them, I really appreciate it. Does the envoy website appear in the browser at least? (local ip from a computer at the same network) Those metrics you're talking about... are they from consumption? through the HA? Regards, |
Hi if I read the answer from Emphase : "It is just that you will need token authentication to access the APIs" |
Until the official integration is fixed (I'd like to help but I'm not a python dev so good luck guys), I'm using this one: https://github.com/briancmpbll/home_assistant_custom_envoy I'm curious, not blaming, why not asking for pull request on the official repository instead of forking it? |
When I access entrez.enphaseenergy.com I have two fields, one for Select System and the other is a drop down with "Select gateway". No matter what I put in Select System the gateway field remains empty, hence I cannot create a token... this seems rather broken if you ask me. |
|
Neat... thanks @alplaurent - would never have figured it out. Thanks to Enphase for sparing even the slightest help tip on the page! (you know... text is so expensive these days...!) |
For those who are asking, history is kept while moving from the official integration to the "new" custom one: I went through this workflow:
|
With the API token that you can get from https://entrez.enphaseenergy.com/ and login with it, it is possible to get all the values from this endpoint https://envoy/api/v1/production/inverters . Would it be possible to rewrite the current plugin that it works with the current official hassio integration? |
one question for everyone. Could you log in the local envoy web? (http or https://envoy.local/ or local ip) Because, I only have one time a message the "unsecure connection", but never reach the local web site. I can do a telnet with 443 or 80 port. |
@alafon, What do you mean with this? Everything until this worked. I'm unable to reconfigure the existing integration and when using the add integration option it says that it already exists. |
@legomannetje, @alafon, It shows "Enphase Envoy (DEV)" but where do I click next? If I select ADD Entry and enter all the information, Local IP address, Enlighten credentials, Serial number and check Enlighten. It doesn't work. |
This seems to highly depend on the https://entrez.enphaseenergy.com/ availability.... |
Going to my envoy url, it looks like they updated the firmware of my envoy to v7... |
Try another browser, it works for me in chrome but not in Safari for example because Safari does not allow to visit "unsecure websites". It does not trust the self-signed certificate. |
THX!... in my case I had to restart the envoy ro reach it. |
You should implement API token usage if possible, this will prevent calling enphase entrez.enphaseenergy.com forever. Edit: after checking my token, it is valid for 365 days to this will have a limited impact to renew it once a year. Would be very nice to have it (much more than the unexpected update from enphase :-) ) |
This happens to me as well. |
Ok, got it to work. So for dummies (like me)
It seems other before me in this trail were able to do it without deleted the old one. Works. But... |
Thanks! I've also just deleted the old entity. I had to reconfigure the energy dashboard settings as well. FYI: After deleting the old Envoy integration the energy dashboard doesn't delete historical data about your solar production! 🎉 |
Works perfect, thanks! |
Thanks, works perfect. |
Sadly no Lifetime production (while this is in the json output), also the whtoday and stuff is now gone, dont see it in the json also (or at least i see it but its 0) |
I did find the HACS version (https://github.com/briancmpbll/home_assistant_custom_envoy) did work for a while. However when my envoy disconnects from Enlighten, it throws HA off - or at least that’s what it looks like. My envoy will go for several hours without phoning home, so both the Enphase web page and HA are out of date. If I reload the integration it will reconnect, but disconnect within minutes. Edit: It appears to me that the firmware update has blocked local access and you have to validate through the Enphase/Enlighten website. If that website is down or overloaded (a frequent situation) you lose connection to the Envoy. This has been an issue for more than 18 months as they slowly rolled out the firmware updates and Enphase has shown no inclination to fix the problem by allowing owners the choice of local access or the “more secure” web validation. |
with firmware 5.X i could enable / disabled the production of energy with a curl command. this is not working in v 7.X anymore. is there another way to make an api call to the gateway and enable/disable power production ? |
Thanks. That worked for me. I had to delete my old integration (for a v5 enphase) before I could trigger the setup process for the v7. |
What does deleting the old integration do with historical data? Do you keep all? |
I had that as well, but it can be fixed manually by briancmpbll/home_assistant_custom_envoy#88 (comment) |
Sadly that didnt work, i tried yesterday, no data whatsoever |
I did the same thing by editing it directly in the /config/custom_components folder and restarting. |
It only worked for my after removing previous configuration. |
For anyone having the "Device is already configured" issue, if you are confident in your abiliities to edit JSON data without making any typos, you can edit your Old:
New:
Only edit the section under "data" and make sure "name" is unchanged. After editing, validate your json with jq, e.g. |
This is what I've been messing about with and it all seems to work locally, so that gives me hope for a fix for this integration as long as Enphase leave the local one alone. I know it seems too good to be true but to programmatically create a token and the ability to send it to the local GW in return for some lovely data is indeed encouraging! |
Also, if anyone is missing the daily total kWh for use with hot water boost or anything, I output to PVOutput, which still works ok, so I just use the PVOutput integration to get the daily total back in for the time-being until some kind person develops a fix. |
So got my token. Where do I add it? |
I have managed to update to the new Enphase Envoy (DEV) integration and I getting data from my IQ once again. Only problem is that the comsumption data is getting messed up somehow. Things seem OK but at around 8am each day there is an erroneous spike in the consumption data, I have no idea where this is coming from. Here is what I am getting from the Energy Dashboard But here is the correct data from Enlighten I guess I need to make a change to my config.yaml file, here is what is currently there and was working fine before the update.template:
sensor:
Any suggestions on what needs to be altered to correct this gratefully recieved. |
I haven't used the new dev integration, mine was more of a potential-programming/informational post. |
For nearly two days I have been getting consistent data using this one: Prior to that it would disappear for a couple of hours and then come back for a few. I have also noticed the connection between the Envoy webpage and Enlighten is more consistent. For the first time I have been able to get the "live" data page up in Enlighten Manager. Until yesterday it always timed out. It doesn't give me any more than the Envoy webpage, but suggests maybe Enphase has improved the link. |
duplicate of #88983 |
The problem
Hello
My Enphase integration has been unavailable for a few days.
I've deleted it but I can't connect despite numerous attempts.
I enter the information (which is correct),
HA tries to connect for about 2 minutes....
and then a "connection failed" message appears.
I've also tried using only the IP address, "Envoy" as the identifier and the serial number, and unchecking the "use Enlighten" box, but the result is the same...
I was in vesrion 2023.06.4. I switched back to 2023.4.5 but I still have the same problem...
I don't know what else to do...
Thanks in advance for your help
What version of Home Assistant Core has the issue?
core-2023.06.4
What was the last working version of Home Assistant Core?
core-2023.4.5
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
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: