Add APsystems EHZI micro hybrid battery inverter #23910
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add support for APsystems EHZI micro hybrid inverter with 2.4kWh battery - Support battery monitoring (power, SOC, energy) via HTTP API - Include battery control capabilities (normal/hold/charge modes) - Tested with hardware at 192.168.20.8, firmware 1.1.4.5 - Power values correctly inverted for evcc battery conventions - Template includes German and English localization
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
vuka1
force-pushed
the
feature/apsystems-ehzi-template
branch
from
73b4868 to
199a850
Compare
andig
changed the title
- Remove trailing spaces from German description - Add newline at end of file to satisfy CI formatting checks
|
I only have the battery connected to my EHZI inverter (no PV panels attached). Is anyone actively using this inverter with PV panels who could help add/ test the template in that configuration? -- bug in setpower case 1: what variable to use to get the needed watt the inverter should charge / decharge (P=...)? |
vuka1
force-pushed
the
feature/apsystems-ehzi-template
branch
2 times, most recently
from
7835fd1 to
32d4980
Compare
|
I cannot find a variable to set the batterie charging / decharging watt's. Is a formula within the template is acceptable? |
Add template for APsystems EHZI hybrid inverter with battery control support. This enables dynamic battery power management for the EHZI system. ## How the EHZI works: The APsystems EHZI is a hybrid inverter that combines PV generation, battery storage, and grid connection. Battery power control is done via HTTP endpoint: - GET http://<host>/getOutputData - reads battery power (batP), SoC (batSoc), and system status - GET http://<host>/setPower?p=<watts> - sets battery charge/discharge power - Positive values = discharge (battery supplies power to home) - Negative values = charge (battery takes power from grid/PV) - Value 0 = hold (no charge/discharge) The EHZI dynamically limits actual power based on battery SoC, temperature, and grid conditions, so requested power may differ from actual power. ## Template features: - Dynamic power matching: Calculates net home demand (homePower - pvPower) and adjusts battery power every watchdog/2 seconds to minimize grid usage - SoC limits: Respects minsoc (minimum SoC for discharge) and maxsoc (maximum SoC for charge) - Battery modes: normal (dynamic), hold (maintain SoC), charge (force charge from grid) - HTTP caching (5s) for faster UI validation and reduced API calls - Watchdog-based continuous power adjustment in normal mode ## Configuration: The template requires one-time activation via evcc UI after adding the battery: 1. Open evcc web interface 2. Click on battery icon or go to Settings 3. Enable "Battery Discharge Control" or set battery mode to "Normal" 4. Watchdog will then run automatically every watchdog/2 seconds ## Known issues and limitations: ### CRITICAL - PV integration missing: The current implementation does NOT consider PV excess power for battery charging. Template only does discharge management (home consumption from battery), but lacks logic to charge battery from PV surplus. This needs to be added. ### Watchdog stability issues: - Watchdog occasionally crashes/stops running without error messages - Root cause unknown - possibly related to evcc's watchdog implementation or script execution failures (curl timeouts, bc calculation errors) - Requires manual reactivation via UI when this occurs - Frequency: Sporadic, not reliably reproducible ### SoC limits not always enforced: - Intermittent issues where battery discharges below minsoc or charges above maxsoc - Possibly related to watchdog script execution timing or race conditions - SoC checks happen in script: if soc <= minsoc, then power=0 - May fail if batterySoc value from API is stale/cached when script runs - Workaround: Lower safety margin (e.g., minsoc=15 instead of 10) ### Power value retrieval architecture: The current approach to get home/pv power values is problematic: ```bash data=$(curl http://127.0.0.1:7070/api/state) home=$(echo "$data" | jq -r ".homePower // 0") pv=$(echo "$data" | jq -r ".pvPower // 0") soc=$(echo "$data" | jq -r ".batterySoc // 50") ``` Issues: - Multiple JSON parsing operations in shell script (slow, fragile) - No direct variable access - must query full API state - Requires curl, jq, bc in system PATH - Complex calculation logic in shell with bc: echo "$home - $pv" | bc - Difficult to debug when values are incorrect Better approach would be: - Template variables that expose homePower, pvPower, batterySoc directly - Native calculation support in template engine instead of shell scripts - Or: dedicated plugin type for dynamic battery control with built-in variables ## Testing: - Tested with EHZI at 192.168.20.8, 2.4kWh battery capacity - Verified SoC limits (minsoc=45%, maxsoc=50%) work when watchdog is running - Confirmed power calculation: homePower - pvPower = battery setpoint - Verified EHZI power sign convention: batP negative = discharge, positive = charge (reversed from evcc convention, template uses * -1 to convert) - HTTP cache reduces UI validation time from 12s to ~4s ## Next steps: 1. Fix PV excess charging logic - battery should charge when pvPower > homePower 2. Investigate watchdog stability issues - add error handling and logging 3. Improve SoC limit enforcement - consider adding hysteresis or safety margins 4. Refactor power value retrieval - propose template engine enhancement or create dedicated battery controller plugin type Related: #<issue-number-if-exists> Fixes: #<issue-number-if-exists>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add support for APsystems EHZI micro hybrid inverter with integrated battery storage and control capabilities.
Hardware Details
Features
Technical Implementation
/getOutputDataand/setPowerTesting
evcc --template-type metermake docsComparison to existing APsystems templates
This EHZI template differs from the existing EZ1 template as: