From ed626b3ab3901c61f507da7f0159fca231c59055 Mon Sep 17 00:00:00 2001 From: Trefor Southwell Date: Sat, 15 Aug 2026 14:45:15 +0100 Subject: [PATCH] fix(fox): bump settings cache version to force-refresh fdpwr_max on upgrade battery_rate_max is only recomputed when get_scheduler() actually makes a live call, which is otherwise gated to once an hour - so a customer upgrading to the capacity_watts() fix kept the old, wrongly-clamped fdpwr_max from their persisted cache while inverter_capacity (recomputed live every publish cycle from cached device_detail) updated immediately. Bumping FOX_SETTINGS_CACHE_VERSION triggers the existing self-heal path that forces one scheduler refresh regardless of cache age. --- apps/predbat/fox.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/predbat/fox.py b/apps/predbat/fox.py index 71074b56c..6a6369434 100644 --- a/apps/predbat/fox.py +++ b/apps/predbat/fox.py @@ -64,7 +64,7 @@ # range/unit/precision to schedule-derived settings) so a persisted cache from before that # change is detected as stale and forces one settings/scheduler refresh regardless of age, # instead of being reused as-is - potentially forever, since nothing else would ever correct it. -FOX_SETTINGS_CACHE_VERSION = 2 +FOX_SETTINGS_CACHE_VERSION = 3 # Storage cache keys for device data persisted between reboots FOX_CACHE_KEYS = ["device_list", "device_detail", "battery_charging_time", "device_settings", "device_settings_unavailable", "device_settings_version", "scheduler_state", "device_values", "device_production_month"]