Home Assistant takes my Enphase Gateway Offline

Energy
1

I've been doing home automation for a while now running HS3, HomeKit, and an Home Bridge and want to add HA to the mix.

I have HS, HA, and HB all running in separate VMs on a M4 MacMini.

The installation of HA went fine and the system found all the supported clients on the network. But I noticed that every time I start HA my Enphase Gateway begins to not update. I've let it go for hours without an updates and eventually have to reboot the Enphase.

I've tried configuring the Enphase plugin, but no help. I've removed the Enphase plugin, again no help.

I'm running a Unifi network with an updated router and switches. I eventually created a firewall policy to block traffic between the HA IP and the Enphase IP but still have the same problem.

Any suggestions on how to resolve the conflict.

2

Is HA the only system communication with the Enphase Gateway or are other systems also communicating with it?

3

There are no local systems accessing the gateway.

For a few weeks I used an HS4 plugin but have removed it.

4

So even without the Enphase_envoy integration configured in HA, the gateway has the issue when HA is running?

HA has a unify integration, are you using that and might that have some influence on your networking? (I'm not familiar with that integration.)

begins to not update

Like not update in the Enphase portal or Enphase App? Or not updating data in HA?

Is there anything in the HA log file that may have some information?

With HA running and Enphase integration configured, enable debug on the HA Enphase integration and let it run for some time in debug mode. That will add more detail to the communication in the log file. This will only reveal the HA side of things of course.

Is the Enphase only on wired connection (preferred) or only on WiFi, and not on both? It happens that a wired Enphase still has the WiFi enabled and causes some switching back and forth between these or connection issues.

5

Thanks for the reply and suggestions.

Normally the Enphase app will update site data to the portal every 15 minutes and will show Live Status in real time. With HA running and no integration loaded, or loaded and not configured, or loaded and configured, the Enphase updates to the portal stop. The Enphase app will then show how long since the last update which is within a few minutes of when HA was started.The Live Status won't display at all.

The Unifi integration is loaded but not configured. I'll try to eliminate it from the equation. Currently the gateway and the HA sever run on different networks (192 and 10) but behaved the same when they were both on the 192 network.

The Enphase gateway is running on the ethernet port with WiFi configured but idle, the cell modem is also idle.

I'll log a few configurations changes and see what happens.

6

Sounds as if the Envoy has no route to Enphase anymore when HA comes on-line.

The Enphase gateway is running on the Ethernet port with WiFi configured but idle, the cell modem is also idle.

As said, multiple interfaces enabled has given reported issues. I would be tempted to try disabling the WIFI and cell if possible.

7

I'll try that this weekend.

Thanks.

8

I removed all integrations, blocked the WiFi connection, no change.

I tried adding and configuring the Enphase integration but the initialization never completed.

Thanks for helping but I'm going to put Home Assistant on hold for a while. I'm not sure what's causing the issue but I've run out of easy fixes and don't have the time to take a deep dive into the problem.

9

That makes sense for now, too bad it wasn't an easy find. I can only help you out with the Enphase integration. Your issues seems more related to HA in general and your network setup specifically. For these I only can offer generic knowledge. Feel free to get back if/when you file like trying another attempt.

I tried adding and configuring the Enphase integration but the initialization never completed.

Initialization also requires a one-time connection from HA to Enphase cloud to obtain a year long valid token. So probably related.