test: move FoxESS/FoxCloud support_discharge_freeze check into test_inverter.py

Wasn't Teslemetry-specific - springfall2008 flagged it on PR review.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: 2 people

apps/predbat/tests/test_inverter.py

@@ -18,6 +18,26 @@
 from predbat import PredBat
 from const import MINUTE_WATT, INVERTER_MAX_RETRY_REST
 from inverter import Inverter, DISCHARGE_TARGET_UNSUPPORTED_MODELS
+from config import INVERTER_DEF
+
+
+def test_foxess_support_discharge_freeze_matches_foxcloud():
+    """
+    FoxESS (modbus) and FoxCloud are the same hardware via two different connection methods - "feed-in
+    first"/freeze export does not hold SoC flat on either, PV above the export limit still charges the
+    battery instead of being clipped (#4207). FoxCloud's entry was already correctly False; FoxESS's was
+    left True, so execute.py's fetch_inverter_data() never disabled set_export_freeze/set_export_freeze_only
+    for modbus users, letting the planner offer a freeze option that couldn't actually do anything on the
+    real inverter.
+    """
+    failed = False
+    if INVERTER_DEF["FoxESS"]["support_discharge_freeze"] is not False:
+        print("ERROR: FoxESS support_discharge_freeze should be False, got {}".format(INVERTER_DEF["FoxESS"]["support_discharge_freeze"]))
+        failed = True
+    if INVERTER_DEF["FoxESS"]["support_discharge_freeze"] != INVERTER_DEF["FoxCloud"]["support_discharge_freeze"]:
+        print("ERROR: FoxESS support_discharge_freeze ({}) should match FoxCloud ({}) - same hardware, different connection method".format(INVERTER_DEF["FoxESS"]["support_discharge_freeze"], INVERTER_DEF["FoxCloud"]["support_discharge_freeze"]))
+        failed = True
+    return failed
 
 
 def dummy_sleep(seconds):
@@ -2539,6 +2559,7 @@ def run_inverter_tests(my_predbat_dummy):
 
     failed = False
     print("**** Running Inverter tests ****")
+    failed |= test_foxess_support_discharge_freeze_matches_foxcloud()
     ha = my_predbat.ha_interface
 
     time_now = my_predbat.now_utc.strftime("%Y-%m-%dT%H:%M:%S%z")

apps/predbat/tests/test_teslemetry.py

@@ -1082,21 +1082,6 @@ def test_teslemetry_inverter_def_tesla():
         assert key in tesla, "TESLA INVERTER_DEF missing key {}".format(key)
 
 
-def test_foxess_support_discharge_freeze_matches_foxcloud():
-    """
-    FoxESS (modbus) and FoxCloud are the same hardware via two different connection methods - "feed-in
-    first"/freeze export does not hold SoC flat on either, PV above the export limit still charges the
-    battery instead of being clipped (#4207). FoxCloud's entry was already correctly False; FoxESS's was
-    left True, so execute.py's fetch_inverter_data() never disabled set_export_freeze/set_export_freeze_only
-    for modbus users, letting the planner offer a freeze option that couldn't actually do anything on the
-    real inverter.
-    """
-    from config import INVERTER_DEF
-
-    assert INVERTER_DEF["FoxESS"]["support_discharge_freeze"] is False
-    assert INVERTER_DEF["FoxESS"]["support_discharge_freeze"] == INVERTER_DEF["FoxCloud"]["support_discharge_freeze"]
-
-
 def test_teslemetry_component_registry_config():
     """Component registry exposes the automatic arg, can_restart, and the schema accepts teslemetry_automatic."""
     from components import COMPONENT_LIST
@@ -1961,7 +1946,6 @@ def test_teslemetry(my_predbat=None):
     test_teslemetry_backup_reserve_drift_correction_refreshes_cache_and_reasserts()
     test_teslemetry_backup_reserve_drift_correction_no_spurious_resend_when_matching()
     test_teslemetry_inverter_def_tesla()
-    test_foxess_support_discharge_freeze_matches_foxcloud()
     test_teslemetry_component_registry_config()
     test_teslemetry_site_info_publishes_rate_and_limit()
     test_teslemetry_site_info_limit_kw_normalised()