This is a HACS custom integration providing an Envoy Legacy HTML production data extension to the Home Assistant Core Enphase Envoy integration for enphase envoys/IQ Gateways.
This custom integration is NOT a replacement for the HA Enphase Envoy integration. You still need to configure the HA Enphase Envoy integration to communicate with any Envoy type. This custom integration registers a custom updater for pyenphase, which is the communication module used by HA Enphase Envoy. Once this updater is registered, Envoy production data for legacy Envoy can be collected by the HA Core Enphase Envoy integration from the HTML pages used by Envoy firmware's < 3.9
You should only deploy this custom integration when running an Enphase Envoy legacy model with firmware before 3.9, either stand-alone or in a mixed environment with newer models. The registered updater is only used for communication to the legacy Envoy, not for communication to the newer models.
As of Home Assistant version 2025.7, the Enphase Envoy integration switched from using httpx library to using the aiohttp library. This is a breaking change for this custom integration. Starting with Home Assistant 2025.7 you must update this custom integration to 1.0.0 or newer.
First production versions. Only use with Home Assistant versions from 2023.12 to 2025.?-1.x.
- Make appropriate backups of you Home Assistant installation and data.
- Install HACS if you haven't already
- Add this GITHUB repository as a custom integration repository in HACS
- Restart Home Assistant
- Go to the HACS Integrations page in HA, select this custom repository and download the
Enphase Envoy legacy supportcustom integration - After download restart Home Assistant.
- Add the custom integration using the home assistant configuration flow and select the `Enphase Envoy Legacy Support' integration
If you decide to install this manually without the use of HACS, then make sure to only place the files in custom_components/enphase_envoy_legacy_support from this repository into the folder /config/custom_components/enphase_envoy_legacy_support on your Home Assistant system.
Once the custom integration is added, no further configuration is needed for this custom integration. All setup of the Envoy is to be done in the HA Core Enphase Envoy integration.
This custom integration or the HA Core Enphase Envoy integration can be added in any order, but as long as this custom integration is not added, HA Core Enphase Envoy can not successfully communicate with the legacy Envoy.
With a fresh Home Assistant installation that needs to communicate with a legacy Envoy best first add this custom integration to enable successful adding of the legacy Envoy next. For Home Assistant installations that went through upgrades and now show the legacy Envoy failing, installation of this custom integration will solve the issues as soon as installed.
For Home Assistant installation currently using another custom integration enabling the legacy Envoy and plan to switch to the HA Core Enphase Envoy, first install this custom integration to prepare for such a switch. As this custom integration registers with pyenphase there's no interaction with other custom integrations. How to migrate from other custom integrations to the HA Core one is not in the scope of this document.
Once the custom integration is added to your system using HACS, configure it as described in Adding Integrations. Search for enphase and select Enphase Envoy Legacy Support
There is no further configuration information needed and the integration is created.
The newly added custom integrations shows in the integrations dashboard
In the integration details it shows as a service. The add service button will not add any more services. Only 1 can be added and is sufficient.
A legacy Envoy only provides production data.
