briancmpbll / home_assistant_custom_envoy

177 stars 77 forks source link

Questions on migrating to new HA Core version #183

Open catsmanac opened 7 months ago

catsmanac commented 7 months ago
          Thank you! You mentioned, migrating features, what features are in the dev version that are not in the core version?

_Originally posted by @GitittomeNow in https://github.com/briancmpbll/home_assistant_custom_envoy/issues/176#issuecomment-1913928181_

catsmanac commented 7 months ago

Moved over from #176

Based on HA 2024.1.5 the core version is missing:

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

catsmanac commented 7 months ago

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.

catsmanac commented 7 months ago

Moved over from #175

  • 3 phase sensors by @posixx. I recently migrated this, not sure yet in which HA release it will surface.

This was released in 2024.2.0

catsmanac commented 7 months ago

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

catsmanac commented 6 months ago

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

catsmanac commented 6 months ago

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.

testuser7 commented 6 months ago

So all functionality has been added to core?

catsmanac commented 6 months ago

So all functionality has been added to core?

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

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.