[BUG] Enphase Envoy (Installer) integration cannot be installed / used in parallel to 'official'/core Enphase Envoy one

[joergbattermann]

Describe the bug
I've been using the official, core Enphase Envoy integration for a while and found out about this one a little while ago. I was curious and wanted to give it a try but even though I could add & download it via HACS, after the HA restart the core integration was broken and could not be loaded anymore and I think it's because both integrations use the same domain (see this and this).

Historically it appears like this one here had a different / *_custom domain but was changed a few commits in so I was wondering if this is known/intentional and if there are any plans to make both integrations to work in parallel given that they do have slightly different functionalities etc?

Thanks!

Account type

• Installer
• DIY / DHZ
• Home Owner (This integration is not (fully) functional with a home owner account!)

Envoy

• Metered with CTs installed

• Metered without CTs

• Standard

• FW version: D7.xxx

• Amount of micro inverters connected: 35

Home Assistant

• Version: 2025.2.x

Additional context

Relevant snippet of Home Assistant error log. 

[vincentwolsink]

Hi! Correct. This was an unlucky design choice in the past. This integration used to be a drop-in replacement with extra functionality. But nowadays the official integration changed a lot and both are no longer compatible.

You would need to remove the configuration for the official integration first and then you can install and configure this one.

[joergbattermann]

Thanks for the quick response @vincentwolsink .. appreciate it!

Is it realistic to keep this issue around with the hope / advocate for this domain / name overlap to being changed? I understand that this would be a (significant) breaking change and I'd certainly not expect it to happen quickly and maybe more akin of announcing it a few times in the next versions' release notes.. but ideally at one point one could just install both (& without tinkering etc).

[vincentwolsink]

Yes, I would like to move the domain at some point. I wonder how much chaos it will cause though 😅

[joergbattermann]

I mean.. what COULD go wrong (other than dashboards and custom templates and all that breaking) ;-) ?

But yeah, that's why I sort of meant.. let people know a couple of versions upfront in each release note leading up to i.e. v0.7.0 or v1.0 or sth and then everyone got enough time to mentally prepare / hold back updating until they have a little bit of time to adjust their customizations around the current naming scheme.

[bartkummel]

I have a similar issue: I'm using the other HACS Enphase integration. But now I want to be able to switch production on and off, so I want to switch to this integration. I also don't want to loose all data that I've collected about energy production in the past.

• Would I need to wait for this integration to change it's domain before I can install it without uninstalling the other one?
• Or can I keep my old data when I uninstall the old integration and then install this one?

[vincentwolsink]

Hi @bartkummel, Home Assistant, does not delete history when you remove an integration.

You can remove the previous one and then install this one. If you make sure the (important) sensors have the same name, history will be there.

[jvrossum]

I downloaded and configured this addon, but it does not start. But the “official” integration is nowhere to be found. So now my old integration is not longer working and your addon is also not working.. The official add on does not show either in the integration list anymore..

[vincentwolsink]

@jvrossum If you can supply me with (error) logs I can check why the integration is not working for you. Otherwise you can uninstall it via HACS and the original integration will show up again.

[corneyl]

Same issue here, I'd like to use this integration next to the 'official' one for controlling the power production. What's needed to change the domain? Is it only changing the DOMAIN in const.py?

[vincentwolsink]

@corneyl

• DOMAIN in const.py
• domain in manifest.json
• Directory name

[corneyl]

@vincentwolsink That works well indeed!