Create the sensors in the first post of this thread. This will give you the import or export values that you can use as a trigger in your automations - If sensor.grid_export_power > 500 do something. It will also track export (and import) amounts
You are on the right track with the ‘difference’. This is how we find out how much grid power is either being imported or exported.
Here is a very simple template sensor that will give you a positive or negative number.
If production is > than consumption, then you will have a positive number to indicate excess power being exported to grid.
- sensor:
- name: Net Power
state_class: measurement
unit_of_measurement: W
device_class: power
icon: mdi:transmission-tower
state: >
{% set production = states('sensor.solar_production') | int %}
{% set consumption = states('sensor.house_consumption') | int %}
{{ (production - consumption) }}
And then here is my automation.
alias: Pool Pump On
description: ''
trigger:
- platform: numeric_state
above: '1100'
for:
hours: 0
minutes: 10
seconds: 0
milliseconds: 0
entity_id: sensor.net_power
condition:
- condition: state
entity_id: switch.sonoff
state: 'off'
action:
- scene: scene.pool_pump_on
- service: notify.notify
data_template:
message: Pool Pump on {{ states('sensor.net_power') }} Watts
If you want a seperate sensor for grid import and grid export, then I suggest reading the post here
Having an issue with envoy after upgrading to 2021.10.6 and on the latest version for envoy ensemble… D6.0.98.210726 is the version of the envoy… how can I get enphase envoy reporting again?
Seems there was a JWT token based security enhancement added to the latest enphase firmware that breaks the API access. Several parties are working on a fix.
Maybe this is the wrong topic, but I noticed that I can;t adjust the refresh time of the integration and it’s currently set at 60 seconds. Is it possible to adjust this via the interface?
Anyone know how to install a second envoy and solar system? I have one solar system installed at my main home. In another country I have second system installed and wanted to add it to my home assistant set up in my main home.
Work is going on to update the HA Core Enphase envoy integration to support the newer token based firmware while maintaining support for the older models. For testing purposes a custom integration Envoy_2_Core_custom_test is made available that can be installed with HACS.
The code is based on @briancmpbll custom integration with required changes to pass HA Core tests. Both are compatible and switching between the 2 is possible. Of course the fine printing states it is for testing and you may find something surfacing specifically for your installation.
Awesome, I’m going to be taking a look at this and see what I can figure out. I just got done setting up the version from @briancmpbll and it works, just need time to digest some things. I will get all my info and post up here when I am all ready to kick off testing.
One thing to be aware of that I’ve seen trip up other people trying to fix broken/old integrations — if there are too many changes, the core reviewers might reject the PR as too difficult to review and request that it it be broken up into smaller PRs.
In one case that I know of p, the “testing” custom (hacs installable) repo remains the only place to get the working code still after about 6 months. I believe there was also a little bit of a catch 22 there because modernizing the integration to use config flow was required to allow the PR to be accepted, but doing so makde the PR much more complicated to review. So the only people who find and install the custom repo get the bug fixes.
The one used as update for Core is actually @briancmpbll custom integrations and up to date with his recent versions updated by @posixx. It needed modifications to pass all pre-commit tests for HA Core and some features added from @vincentwolsink and @mnederlof, inlcuding local token storage.
Small step changes is understandable, however this case brought in a custom integration in one go replacing current one. Then 21 more commits are added. And current one is just broken while the new code is also avaialble in custom integration format for testing and those that need it. So will be interesting to see what happens.
Some major updates to the Enphase integration have been merged into HA Core for release in 2023.9 in a few weeks. These updates include some additional sensors and features for the Enphase Ensemble (Enpower/IQ System Controller and Encharge/IQ Battery) system. So far I’ve been the only person that actually has the Enpower and Encharge batteries to test with.
Is there anyone else out there with an Ensemble setup that would be willing to submit some test data for us? We need some fixture files for our unit tests, and have written a script that will collect them.
Set ENVOY_USERNAME and ENVOY_PASSWORD environment variables to your Enlighten (cloud) credentials
Run devtools/fixture_collector.py
This will query your envoy for a bunch of data and generate a zip file containing the responses. The response files can be added to a folder under tests/fixtures and submitted as a PR to the pyenphase repository
Also if anyone has a generator connected to their Ensemble system, I can send over a modified fixture collector script that will pull generator data so we can implement that in the future