Ik heb de moeite genomen om eens dat 'beruchte'
topic goed door te lezen (440 berichten) over het sluiten / dichtzetten van de API. Dat topic is in juli 2021 gestart nadat een gebruiker merkte dat de API niet meer werkte. Deze gebruiker lijkt overigens uit Australië te komen, en alleen daar speelt het probleem.
Een aantal punten, eigenlijk soort samenvatting van dat topic:
Er wordt op gehint dat er evt een 'premium' dienst komt, waar je voor moet betalen om nog lokale data te kunnen krijgen:
Phillips_1325
9 months ago
Here is likely the real answer:
Premium Monitoring with Enlighten Manager
Enlighten Manager lets you monitor advanced system performance with a host of other features (afbeelding). Upgrade today with a one-time subscription fee of 349 AUD or a monthly subscription of 14.99 AUD.
* Get system performance benchmarking to ensure your system is performing at an optimal level.
* Get advanced production data at a per panel level, including power output time lapses etc to really get to know your system.
* Get advanced email notifications that can be customised to various parameters in your system.
Click here to know more about the different Enlighten offerings, new features and benefits.
So in other words, Enphase now expects you to pay for access to data that until the firmware upgrade used to be free.. Unimpressed to say the least. Be interested to know what legal options are available considering they have chosen to push out a firmware update which has crippled pre-existing functionality without my explicit consent...
===
Er wordt gerept dat er een API token zou zijn, welke 6 maanden geldig is. Deze zou via
deze link te generen zijn (niet geprobeerd, wil mijn HA en PVOutput niet om zeep helpen).
Iemand anders zegt dat deze maar 1 of 7 dagen geldig zijn...
del13r
4 months ago
Hi @Jeremy Walton (Moderator)
using information others have posted here:
Comissioned tokens have a 1 hour expiry date.
Uncomissioned tokens have 7 days expiry date.
How do we get these 6 month tokens you mentioned?
Een moderator geeft later een link naar een technical briefing:
klik hier
Hierin wordt o.a. beschreven hoe je een 6 maand-geldig API token kan genereren.
===
Gebruikers melden dat ze de toegang kwijt zijn tot de productie pagina:
Kelland_9005
8 months ago
Hi, I'll let @Phillips_1325 reply in case this is wrong, but I've lost access to
http://X.X.X.X/api/v1/production it now is forced to https, and requires authentication via some undocumented token process.
Bij mij is dit nog gewoon bereikbaar. En laat zien:
code:
1
2
3
4
5
6
| {
"wattHoursToday": 18510,
"wattHoursSevenDays": 122454,
"wattHoursLifetime": 4653867,
"wattsNow": -9
} |
===
Het lijkt erop dat het pas speelt bij firmware versie 7.x.x, welke in Europa (nog) niet is uitgerold.
Momenteel zitten 'we' hier op 5.0.55 of 5.0.62.
===
Een gebruiker meldt dat een Enphase medewerker heeft gebeld en aangegeven heeft dat in versie 7.x.x. de API toegang gewoon beschikbaar blijft:
McAlary_2587
7 months ago
I just had a really lovely call from Jeremy Walton at Enphase and he assured me that current functionality in 5.x regarding local API access will continue to be available in 7.x upon its general/wider release.
Thank you Jeremy this is a fantastic outcome for Enphase's customer base.
Echter spreekt een andere gebruiker dat even later tegen:
Kluttz_6334
7 months ago
McAlary, I just had a conversation with an engineer on this and had a much different outcome to the discussion than what you had so this may not be a done deal. Also, the answer to your questions may be true but skirting by on a technicality that I didn't give them in my call. Although the API may still be present going forward, which will likely be true, my question was will it also be accessible via LOCAL credentials that do not require cloud access. The answer to this was most definitely a no.
===
De local API lijkt wel beschikbaar te blijven, maar Enphase wil gebruik maken van een token die maar een aantal maanden geldig is:
McAlary_2587
7 months ago
@Anderson_3096 @JustPoet I confirmed from talking to enphase last week, as have others, that their plan is not to remove the local API, the problem is that they are going to require a cloud generated token to access it - thereby introducing an external dependency on their cloud to access a local system where previously no such dependency existed. You could get the data even if envoy was in a remote jungle or enphase cloud was suddenly unavailable. That's what has commentators concerned: needing their cloud to access a local system.
At the moment their workaround is to downgrade affected users to 5.0.55 , but that may have it's own ramifications for future system expansion and enlighten data upload, it remains to be seen.
The ideal solution is that enphase simply continue to provide a read-only API endpoint on the envoy with no token required.
en:
McAlary_2587
7 months ago
@Kluttz_6334 I got a call from sales in Australia, and they apparently put my letter to the development team who said the local API isn't going away but IS going behind a cloud token.
===
En dan een belangrijke post van 1 van de moderators, 2 maanden geleden:
Hi all, I took this up with the relevant team for you and received the following information for you.
* We understand the feature request and we want to thank customers here for their ideas and their patience with Enphase as we try to respond to the same
* We have a set of features available in the near term which do not meet the exact request but provide insight into the system while we work on newer features
* In Q2 2022 we will be deploying the gateway software 7.x release to systems.
* Gateway software 7.x provides the ability to home owners to do 2 levels of local monitoring
* In the absence of internet connectivity the app tries to reach the gateway directly via the local wifi router and displays a live streaming view of the current system status including power production and home consumption (and if applicable power export to grid)
* If the app is unable to connect to the gateway via the wifi router due to any reason the app provides direction to the homeowner to connect to the gateway’s wifi network directly and fetches the same live streaming view (described above) via the direct wifi connection
* In the future we intend to extend these features to cover more information from the gateway
* For advanced users who want to connect Enphase’s solution to home energy automation solutions – we do not plan to enhance the gateway software with MQTT clients in the near term however the APIs that have existed on the gateway continue to remain accessible with the caveat of requiring a security token (that currently has a 6 month expiry at maximum). We will be looking at expanding the expiry of the token based on the customer feedback received from the our users. We do not have a concrete timeline for this yet but the product team is in discussions with security architects and engineering on this feature now and we will have better visibility in a month or so.
===
Laatste antwoord van de moderator, welke ook momenteel als 'beste antwoord' gemarkeerd staat:
Jeremy Walton (Moderator)
a month ago
We understand that certain users want their energy systems connected only locally, and to dispense with our token authentication process. However, our token authentication solution is currently applicable to all locally-connected Envoys, and we stand by this decision which we feel gives an enhanced level of security for such systems, where unauthorized access is largely in the hands of the system-owner. To be clear, we did not move to token-based authentication to obstruct users from obtaining their own data or to somehow profit from that (which we do not).
To clarify a misunderstanding around this issue, tokens for system-owners are valid for 6 months and therefore present extremely low inconvenience and risk that a token expires during an extended outage. If you are receiving a shorter token (1 hour or 12 hours) then the problem is likely that you are logging in as “installer” and you will need to use a “system-owner” enlighten account instead. Customer Service can assist with this.
===
Wat is er eigenlijk uit opmaak, is dat ze over willen gaan van een life-time API token (wat we nu hebben, zoals voor PV Output of Home Assistant) naar eentje die bijvoorbeeld 6 maanden geldig is. Dit om de 'beveiliging' te verbeteren (zoals het idee dat je je wachtwoord af en toe moet veranderen). Als dat alles is, dus dat we straks 2x per jaar de API key moeten aanpassen is onze setups, maar wel daarmee de lokale toegang behouden, dan kan ik daar wel mee leven.
Echter, dit speelt allemaal in Australië op dit moment, en (nog) niet in Europa!