I am suffering from frequent connectivity issues with my Enphase Envoy. This is just today and it can be seen during the night were many spots when no data was taken and around 9am nearly 45min:
I’m not a big fan of Enphase for the reason you highlight here. Also, it is my understanding that the integration gets data from the cloud, Enphase’s servers, not directly from device at your location, in my case, the Envoy. I believe that what you’re seeing is the myriad of cloud issues.
I have access to the Envoy’s web page. I have a routine that “scrapes” the System Energy Production page for Currently (current power) and and Since Installation (total energy captured … but only 3 digits). I reformat into a JSON which I publish to an MQTT broker. In HA I have installed the MQTT integration. In the config folder I create MQTT.yaml (linked in configuration.yaml) which has the formatting to extract the data from the JSON. I end up with a sensor.envoypower and sensor.envoytotal.
Yup, a lot of friggin’ hoops. Such is the life of the cloud-o-phobe. (Is it paranoia if the fear is justified?)
If you didn’t get all of that, send me a message. Your message will motivate me to publish my documentation here.
Ok, Enphase user here. No problem ever. Must say. No wifi, only cables. As far as I know the envoy only connects to 2.4ghz wifi which is a highly used frequency band. So it probable the wifi. The Enphase integration is only using local polling at my place.
Integration accesses the Envoy directly over the local network. It only uses the cloud to get a new token at install time or a month before the 12 month token expires to refresh it.
Wifi has been reported as shaky interface on more occasions. WWAN is no option, Envoy should be on same local network as HA. If it switches to WWAN the HA will loose connection. Can that be the issue?
