Closed dmac001 closed 8 months ago
Hello,
the error ERROR:root:--> fetch_meter_stream(): Received HTTP status code 401. Restarting the driver in 60 seconds.
has nothing to do with the self signed certificate. See HTTP status code 401.
Please read "💡 NOTE" in the README.md. Very likely your token has the owner
user and not the installer
one.
I understand, my token is owner. Since the readme references an 2023.06.06 update, I assumed this has been resolved by now, especially considering your recent beta updates.
The point I was trying to make was that I can click-through the 401 error on my desktop browser and view the production json.
I'll keep checking for future updates. Thank you.
UPDATE (2023.06.06): The needed API /stream/meter will be available with the owner token after the release of a firmware update at the end of June. See Make "/stream/meter" available with "owner" token. After this happen I release the next stable release of this driver.
Unfortunately there did not happen much from the Enphase side. To increase a bit the pressure it would help, if you and others also comment under the linked article above in the enphase community.
You could reach out to your installer and ask them to give you installer rights or contact Enphase by linking to the community entry above and request the installer rights.
From latest intel that I got from an Enphase employee it will be changed with v8 of the firmware that will be shipped in Q2/Q3 2024 for Europe.
Hello,
This is a great project!!!
I'm at a bit of a loss here -- when running enphase-envoy code on Venus OS 3.10~38, RPi 3B+., the log file is showing 'Received HTTP status code 401'. The enphase-envoy code does not click through this warning.
On my Windows Chrome/Edge browsers, I can click-through the "Your connection is not private...", ERR_CERT_AUTHORITY_INVALID and the page redirects to the Enphase home https[Enphase IP]/home#overview. If I open https://10.10.0.239:443/production.json?details=1, I get a page of production json,
Your dbus-enphse-envoy code is very close to working. Is there a way to ignore the 401 security warning and continue and add the proper https authentication?
Excerpt from log file,
Thank you, Don