Potential Impact of Enphase's Local Web Discontinuation on Home Assistant Plugin?
Neowam opened this issue · comments
Hello Vincent,
I hope you're doing well. I've been using your Home Assistant plugin for Enphase, and I wanted to share a recent response I received from Enphase Support, as it might have implications for your add-on:
Hi Werner,
Thank you for contacting Enphase Energy.
I apologize for the delay in response.
Regarding the Errors on ITK GUI page,
-
[missing "en.envoy_backbone.overview.enpowers_summary.connected.undefined" translation]
-
[missing %{db_size} value] ([missing %{percent} value]% full)
The Empower is the Enphase smart switch which is now termed an IQ system controller. These system controllers are a part of the battery system.
By default, the gateway will try to recognize the IQ system controller. Now that your site is a PV system without a battery, the Gateway S throws that error.
You may ignore the error as yours is not a battery system or you may reach your installer to know more details on the Enphase battery in your location https://support.enphase.com/s/question/0D53m00009Cf3seCAB/envoys-not-displaying-enpower-connection-state-and-database-size-after-firmware-update-to-d7428
I suggest you use Enlighten or ITK to view the Gateway data as Local Web is no longer a part of the development.
I appreciate your patience with us.
We are constantly striving to provide excellent customer service at Enphase Energy
Please feel free to contact us for any further help. Furthermore, You can also contact our technical support at (877) 797- 4743 if you have any additional queries.
Have a great day ahead!
Thanks & Regards,
Brahmaduth
Enphase Energy | Customer Support Engineer
The part that caught my attention was: "I suggest you use Enlighten or ITK to view the Gateway data as Local Web is no longer a part of the development." I wanted to bring this to your notice specifically. If your code or the functionality of the add-on relies on the Local Web aspect of Enphase, this change could be significant.
I'd appreciate your insights on how this might affect the plugin, and if there are any updates or modifications that might be needed in the future.
Thank you for all the effort you've put into the plugin, and I look forward to your feedback.
Best regards,
Werner
Hi @Neowam, I assume they are talking about the local web GUI, not the api endpoints. The integration only interacts with the api directly (no GUI scraping) so we should be fine.