GithubHelp home page GithubHelp logo

Comments (8)

catsmanac avatar catsmanac commented on August 17, 2024 1

For those that want to run the HA core integration but can't because they still have an Envoy legacy with firmware <3.9 there's a custom integration enphase_envoy_legacy_support that does not replace the HA Core but is installed as a separate custom integration with name ha_enphase_envoy_with_legacy and registers the required webscraper with the HA Core Enphase Envoy integration. All communication and processing is done by the HA Core integration and it enables running Legacy Envoy, either alone or in mixed environment with newer models, all served by the HA Core integration.

from home_assistant_custom_envoy.

catsmanac avatar catsmanac commented on August 17, 2024

Moved over from #176

Based on HA 2024.1.5 the core version is missing:

  • 3 phase sensors by @posixx. I recently migrated this, not sure yet in which HA release it will surface.
  • Lifetime net-consumption and net-production ( V0.0.17, v0.0.18, v0.0.19 ) by @cddu33 and @testuser7. I've migrated that to pyenphase, the library used by HA Core, but it still needs to be added to HA Core.
  • Battery Energy charge and discharge in this custom integration is based on change events in % load in the battery. HA Core doesn't provide that and you need to build something for it. It's discussed in a community topic.

The community topic also has experiences in switching from this one to core.

from home_assistant_custom_envoy.

catsmanac avatar catsmanac commented on August 17, 2024

Moved over from #175

What I forgot to add to the list is that the HA Core does NOT support old Envoy models with firmware BEFORE 3.9. For those, data is coming from an HTML Page and HA does not allow web page scraping in core components.

The pyenphase module used by HA Core module has an options for customhooks and it relatively easy to extend it to get the data for legacy models as well. That extension would be a custom integration with the extension as custom part and using the core component for others. That would support installations with mixed legacy and modern ones like this one does.

from home_assistant_custom_envoy.

catsmanac avatar catsmanac commented on August 17, 2024

Moved over from #175

This was released in 2024.2.0

from home_assistant_custom_envoy.

catsmanac avatar catsmanac commented on August 17, 2024

For experiences with migrations see the community blog: https://community.home-assistant.io/t/switching-from-enphase-envoy-dev-back-to-core/611391

from home_assistant_custom_envoy.

catsmanac avatar catsmanac commented on August 17, 2024

Grid import/export is now available in HA core 2024.3 as net consumption and net production.

from home_assistant_custom_envoy.

testuser7 avatar testuser7 commented on August 17, 2024

So all functionality has been added to core?

from home_assistant_custom_envoy.

catsmanac avatar catsmanac commented on August 17, 2024

So all functionality has been added to core?

At a high level yes, but not in same detail.

  • Core doesn't have the options that this one has to change timeouts, retries or not use the production json.
  • Core doesn't have the Power Factor nor Current for the CTs.
  • Core is only using ivp/meters/readings and not ivp/meters/reports
  • Core has Grid Status from different source as this one.
  • Core has support for enpower and encharge including operating switches and modes
  • Battery Energy charge and discharge in this custom integration is based on change events in % load in the battery.
    • HA Core doesn't provide that and you need to build something for it. The current ones can be re-used or re-build the same way but require some work I expect. Integrating battery power is discussed in a community topic.
    • Core will get support for a 3th CT for battery storage if you have this installed and that can be used for energy dashboard.
  • To run core with legacy the additonal custom integration enphase_envoy_legacy_support needs to be installed as well

So see if it suits your needs best try it in a docker container or some other way before switching. And https://community.home-assistant.io/t/switching-from-enphase-envoy-dev-back-to-core/611391 has some experiences on how it was done. And as good habbit, make backups before changing anything.

from home_assistant_custom_envoy.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.