Enphase Envoy integration - Recent firmware changes by Enphase has broken integration

[scottyphillips]

The problem

Hi Team,

Enphase has recently pushed out an upgrade to their firmware for the Envoy-S gateway.
The new firmware version on the gateway is D7.0.43.

The breaking change is that all http: requests are now redirected to https: and that authorisation is required using either an enlighten account or a token that is generated through some unknown means on the Enlighten website.

This means that previous open accessibility to local API calls on the gateway (e.g http://192.168.1.6:production.json) throwing 401 authorisation errors, redirecting to https://192.168.1.6/home ; and are no longer working with the Home Assistant integration.

What this means for the integration is that adding it via either GUI or YAML is not working. Ive noticed adding via the GUI requests a username and password, but I believe this is the 'envoy' username and password which was part of the previous firmware version.

So, Home Assistant hasn't broken this integration, Enphase has, but im raising the bug report anyway so the applicable integration maintainer is aware of the issue.

What is version of Home Assistant Core has the issue?

2021.6.3

What was the last working version of Home Assistant Core?

2021.6.3

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Enphase Envoy

Link to integration documentation on our website

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

When trying to access http://10.X.X.X/production.json for example, the Envoy is redirecting to the following splash page:

If you then log in with Enlighten credentials, you are then able to access the production JSON data.

[probot-home-assistant]

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

[probot-home-assistant]

Hey there @gtdiehl, mind taking a look at this issue as its been labeled with an integration (enphase_envoy) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[vk2him]

You can generate the required installer password by running this Android app - I can confirm it works - I don't have an Android phone but I could load it on my Nvidia Shield.

https://thecomputerperson.wordpress.com/2016/08/28/reverse-engineering-the-enphase-installer-toolkit/

[mikeykau]

You can generate the required installer password by running this Android app - I can confirm it works - I don't have an Android phone but I could load it on my Nvidia Shield.

https://thecomputerperson.wordpress.com/2016/08/28/reverse-engineering-the-enphase-installer-toolkit/

I don't think this now works on the new firmware, even Installer login throws you to https://entrez.enphaseenergy.com/ where the same end user Enlighten account also gives you Installer access.

[vk2him]

Interesting - how do I prevent Enphase pushing that firmware to me? I still have:

Software Version
D5.0.48

[JackKelly]

Just helping to join the dots... Here's the relevant discussion on the Enphase community forum: https://community.enphase.com/s/question/0D53m00006ySLuR/unimpressed-with-loss-of-local-api-connectivity-to-envoys

(As of yet, no useful answers from Enphase)

[scottyphillips]

Yes that was me who raised that comment on the discussion boards, im a bit irate lol, but I expect the answer will be along the lines of "its for security reasons", "Local API connectivity was always an unsupported feature", "you can use the app", or "most of our users have no issues using cloud" 😡

[sbauza]

It looks to me this issue is on the wrong project. While Home Assistants supports the Envoy integration, it uses a specific pypi project for this : https://pypi.org/project/envoy-reader/

Could you @scottyphillips then please report this issue to https://github.com/jesserizzo/envoy_reader/issues ?

Thanks.

[scottyphillips]

Or you could report it @sbauza? 🤷🏼‍♂️

[sbauza]

Or you could report it @sbauza? 🤷🏼‍♂️

I can't reproduce your problem as I'm still using an old firmware.

[scottyphillips]

The Envoy integration is an officially supported integration, and if it’s not compatible with the upgraded firmware then at the very least the integration maintainer can update the documentation to let people know about the limitation? It’s not unreasonable to raise an issue here if the integration is not actually working for a number of us.. the comment that I raised the issue against the wrong repo is simply incorrect…