-
-
Notifications
You must be signed in to change notification settings - Fork 32.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enphase Envoy integration is not showing the Envoy Lifetime battery energy charged and discharged entities #115923
Comments
Hey there @bdraco, @cgarwood, @dgomes, @joostlek, @catsmanac, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) enphase_envoy documentation |
Hi @jupsoleil, you need an installed storage Current Transformer (CT) for this. Your diagnostics file only shows a production and net-consumption CT. The DEV integration I know calculates charge/discharge from changes in battery state-of-charge values changes. If yours is that DEV integration, you can implement those calculations yourself based on value changes in soc using HA templates. (When soc goes up, change is added to charge, when soc goes down change is added to discharge entity). |
Hello @catsmanac , Same for me. How do we install a storage Current Transformer ? |
Hi @jmcollin78, if you want Enphase CT you probably need to check with your installer if it's an option. I only know how to grab the data from the Envoy when it's there, not how to configure the Envoy in detail. The IQ Combiner box comes with battery CT and has an Envoy internally. This suggest the Envoy can be set to a mode that recognizes a storage CT. I think the max number of CT's that can be connected to an Envoy is 6, so if you have 3 phase CT for production and consumption's there may be no option to add more, unless combining phases. For single or split phase operation it might fit. As said, your installer should be able to give some advise and discuss options. For some documents search for IQ-IQ-Combiner-5-5C-DSH-00007-3.0-EN-US-2024-03-01.pdf and/or IQ-Combiner-5-5C-QIG-EN-US-Rev05-2023-07-13-PCS.pdf or first part of these names. These are the US docs I found when I looked for it. The alternative is getting some none Enphase CT clamps on the battery wires and connect these to Home assistant for use with the Energy dashboard. There's HA integrations that offer connectivity for those and let you achieve the same. |
Ah ok. I guess this was an addon or integration or something like that. You mean it is a physical hardware component. |
Yes it is. The integration can get it's data, but it has to be installed and configured. |
ok. I will try to find out how to install CT in the Envoy gateway. |
@jmcollin78, since you have battery an CT, you have a look at briancmpbll/home_assistant_custom_envoy#195 on how envoy may report wrong values for grid import/export in multi phase systems. |
I manage to calculate one myself with this sensor template (can help someone):
Then I add two Helpers of Rieman integration to transform this into energy. And that's it. |
@home-assistant close |
The problem
As described on https://www.home-assistant.io/integrations/enphase_envoy/#energy-dashboard I would like to add the batteries to the energy dashboard, but these entities don't exist.
They did exist when using the DEV version which I just removed - I migrated to the core version this weekend (they were called sensor.mrsolar_battery_energy_discharged and sensor.mrsolar_battery_energy_charged).
What version of Home Assistant Core has the issue?
core-2024.4.3
What was the last working version of Home Assistant Core?
core-2024.4.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Enphase Envoy
Link to integration documentation on our website
https://www.home-assistant.io/integrations/enphase_envoy#energy-dashboard
Diagnostics information
config_entry-enphase_envoy-bb07a766489112773117444b52a434b5.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: