You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 68ad0c8
Browse filesBrowse the repository at this point in the historyBrowse files
fix(inverter): read and write the rate per inverter, so a mixed GE Cloud fleet sees the 3-phase unit (#5359)
Review of the Freeze Export change found that in a GE Cloud fleet mixing a unit
with a power register and a 3-phase one, the 3-phase inverter was bound to no
rate entity at all: auto-config withheld the percentage rate for the whole
fleet when any device had a power register, so its grid_charge_only mark was
never read and Freeze Export stayed on.
GE Cloud auto-config now binds the percentage rate per device, for a device
with no power register only. The inverter asks its own entry which control it
is bound to rather than whether the setting exists for the fleet, which is the
read and write fault in #5359: a power-register inverter no longer reads a
silent 100% from an empty percentage entry, and each inverter is written
through the control it has.
The docs now say the AC-coupled 3-phase model is treated the same way as a
precaution, not as a confirmed hardware limit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
assertcaptured["pause_mode"][1] =="select.predbat_gecloud_battery002_pause_battery", "automatic_config's fleet gate binds pause on the second device"
6120
-
assertcaptured["charge_rate_percent"] isNone, "automatic_config's fleet gate withholds the percentage rates"
6121
+
assertcaptured["charge_rate_percent"] == [None, "number.predbat_gecloud_battery002_inverter_charge_power_percentage"], "the percentage charge rate is bound for the device with no power register only"
6122
+
assertcaptured["discharge_rate_percent"] == [None, "number.predbat_gecloud_battery002_inverter_discharge_power_percentage"], "the percentage discharge rate likewise"
6123
+
assertcaptured["charge_rate"][1] isNoneandcaptured["charge_rate"][0] isnotNone, "the power register is bound for the device that has it only"
6121
6124
second=records[1]["entities"]
6122
6125
assertsecond["reserve"]["entity_id"] =="number.predbat_gecloud_battery002_battery_reserve_percent", "the per-device candidate choice"
Copy file name to clipboardExpand all lines: docs/inverter-setup.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -173,9 +173,11 @@ This is being worked on by the author of GivTCP, e.g. see [GivTCP issue: unable
173
173
- Set geserial to your inverter serial number
174
174
- If you set **ge_cloud_automatic** to `true` in `apps.yaml` then Predbat will auto-configure itself to use the appropriate GE Cloud controls and will ignore any inverter and battery controls set in `apps.yaml`
175
175
- Make sure that the 'discharge down to' registers are set to 4% and charge and discharge slots 2, 3 and 4 are disabled in the portal by setting the start and end times to 00:00 (if you have them).
176
-
- Freeze Export is not available on GivEnergy 3-phase inverters, whether controlled through GE Cloud or through the Predbat hub.
177
-
These inverters have no battery pause setting and their charge rate only limits charging from the grid, so solar would carry on charging the battery during a Freeze Export slot.
178
-
Predbat detects this, logs that Freeze Export is not supported and stops planning it; forced export is not affected.
176
+
- Predbat does not use Freeze Export on GivEnergy 3-phase inverters, whether controlled through GE Cloud or through the Predbat hub.
177
+
On the 3-phase hybrid there is no battery pause setting and the charge rate only limits charging from the grid, so solar carries on charging the battery during a Freeze Export slot.
178
+
The AC-coupled 3-phase model is treated the same way as a precaution; it has not been checked and may in fact be able to hold.
179
+
Predbat detects these inverters, logs that Freeze Export is not supported and stops planning it; forced export is not affected.
180
+
If any inverter in a multi-inverter system does not support Freeze Export then it is turned off for all of them.
179
181
- If you have set **ge_cloud_automatic** to `true` and the GE Cloud does not return accurate **load_today** energy information, you can [override the GE Cloud load data](apps-yaml.md) by creating a custom template sensor and setting **ge_cloud_load_today_ignore** to true in `apps.yaml`.
180
182
- The charge/export slot start and end times are stored by GivEnergy in the timezone set on your GivEnergy account. Predbat reads this timezone from the GivEnergy account details and translates the slot times into
181
183
the Predbat **timezone** setting, so the times shown on the Predbat select entities may differ from those shown in the GivEnergy portal if the two timezones do not match.
0 commit comments