fix(enphase): treat a pending schedule family as supported

The cloud reports a schedule family as scheduleStatus "pending" while a
change settles on the gateway - the normal state straight after any write
Predbat makes. Only "active"/"enabled"/"supported"/"available" counted as
supported, so a site with a perfectly good charge-from-grid family was
judged incapable of it, automatic_config raised and run() returned False:

  Warn: Automatic configuration skipped - Charge-from-grid (CFG)
  scheduling not supported on this site, cannot configure

seen on a site whose cfg family held an active schedule and whose profile
reported scheduleSupported true for both cfg and dtg.

"pending" now counts as supported, and so does any family that actually
holds a schedule, whatever the status string says. "not_supported" still
reports unsupported.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: springfall2008

apps/predbat/enphase.py

@@ -1334,10 +1334,14 @@ async def get_schedules(self, site_id):
                 entry = details[0] if details else {}
             details = await self._prune_sibling_schedules(site_id, family_key, details, entry)
             # "supported" gates whether Predbat can use this schedule family. Real accounts report
-            # a per-family scheduleStatus ("active" seen so far); treat the usable statuses as
-            # supported, with a fallback to the (unverified) boolean flags.
+            # a per-family scheduleStatus; "active" and "pending" have both been seen, and
+            # "not_supported" is how a genuinely unavailable family reports. "pending" only means a
+            # schedule change is still settling on the gateway - which is the normal state straight
+            # after any write Predbat makes - so it must not be read as unsupported, or Predbat
+            # decides mid-run that the site cannot charge from grid and abandons configuration.
+            # A family that actually holds a schedule is supported whatever the status says.
             status_text = str(family_data.get("scheduleStatus", "")).strip().lower()
-            supported = status_text in ("active", "enabled", "supported", "available") or bool(family_data.get("scheduleSupported") or family_data.get("forceScheduleSupported"))
+            supported = status_text in ("active", "enabled", "supported", "available", "pending") or bool(details) or bool(family_data.get("scheduleSupported") or family_data.get("forceScheduleSupported"))
             parsed[family_key] = {
                 "id": entry.get("scheduleId") or entry.get("id"),
                 "startTime": entry.get("startTime"),

apps/predbat/tests/test_enphase_api.py

@@ -840,6 +840,28 @@ def test_get_schedules_supported_from_status():
     assert api.dtg_supported("12345") is False  # 'not_supported' status
 
 
+def test_get_schedules_pending_family_is_still_supported():
+    """A family whose scheduleStatus is 'pending' is supported - a write is in flight, that is all.
+
+    The cloud reports a family as 'pending' while a schedule change settles on the gateway, which
+    happens right after any write Predbat makes. Treating that as unsupported made Predbat decide
+    the site could not do charge-from-grid at all and abandon automatic configuration, even with an
+    active schedule sitting in the family.
+    """
+    api = MockEnphaseAPI()
+    detail = {"scheduleId": "c1", "startTime": "04:30", "endTime": "04:40", "limit": 5, "scheduleType": "CFG", "isDeleted": False, "isEnabled": True, "scheduleStatus": "active"}
+    payload = {
+        "type": "BATTERY_SCHEDULES_CONFIG",
+        "cfg": {"scheduleStatus": "pending", "count": 1, "details": [detail]},
+        "dtg": {"scheduleStatus": "pending", "count": 1, "details": [dict(detail, scheduleId="d1", scheduleType="DTG")]},
+        "rbd": {"scheduleStatus": "active", "count": 0},
+    }
+    api.set_http_response("/service/batteryConfig/api/v1/battery/sites/12345/schedules", 200, payload)
+    run_async(api.get_schedules("12345"))
+    assert api.schedules["12345"]["cfg"]["supported"] is True
+    assert api.dtg_supported("12345") is True
+
+
 def test_inverter_def_enphase():
     """EnphaseCloud INVERTER_DEF exists with the agreed capability flags."""
     from config import INVERTER_DEF
@@ -1943,6 +1965,7 @@ def run_enphase_api_tests(my_predbat):
     test_automatic_config_no_dtg_raises()
     test_automatic_config_no_charge_support_raises()
     test_get_schedules_supported_from_status()
+    test_get_schedules_pending_family_is_still_supported()
     test_inverter_def_enphase()
     test_run_first_polls_all_tiers()
     test_get_today()