Trying to set up the EnPhase binding. When adding the thing (bridge to the local enphase gateway) as per the instructions, it gets created, but communications fails with the following error: COMMUNICATION_ERROR
Could not retrieve data: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Access to the local gateway requires an accessToken (which I have), but I see no way to provide it via the binding.
Which enphase device do you have? The binding works for the Envoy gateway. The message suggests it tries to use a https connection, which is not needed as far as I know and I’m also not familiar with the access token. What configures did you use?
It is a regular envoy gateway (Model ENV-IQ-AM1-240 M). However I think the last few envoy firmware revisons (I have D7.0.107), requires an access token to access the local gateway. https://support.enphase.com/s/question/0D53m00007a2WcDCAU/instructions-to-get-access-token
Hmm, it looks like they changed the local API access with v7 and that they also promise to change/improve the local API. This means the current version of the binding doesn’t support this. My own system seem to be stuck on a old version from 2018.
Yes, they have rolled out version v4 of the API which uses OAuth. They are deprecating the old API in October.
Is there any further development with this error? I have just had an Enphase system installed and I am getting the same error with V7.
The documents at: The Enlighten Systems API talk about using the REST API. Can we get data from that source?
I also appear to be in the same boat - new Enphase system, PKIX error as soon as I create the Envoy thing in OH. I found the process for getting an access token mildly annoying but it did the job (and it’s valid for a year - I can put up with the annoyance of obtaining a new one manually once a year, even though I may automate it later)… so now I can get the data using my web browser at envoy.local, I just can’t get any data into openHAB, which is very important to me! Would love to know if there are plans to bring the Enphase binding up to date to support the new firmware.