diff --git a/apps/predbat/config.py b/apps/predbat/config.py
index 551d308b..5d22eb6d 100644
--- a/apps/predbat/config.py
+++ b/apps/predbat/config.py
@@ -323,7 +323,7 @@
         "unit": "p/kWh",
         "icon": "mdi:currency-usd",
         "enable": "expert_mode",
-        "default": 0.5,
+        "default": 0,
     },
     {
         "name": "metric_battery_value_scaling",
diff --git a/docs/customisation.md b/docs/customisation.md
index 408aa3be..fbc75057 100644
--- a/docs/customisation.md
+++ b/docs/customisation.md
@@ -120,12 +120,12 @@ This cost will be included in Predbat's cost optimisation plan when it decides w
 _NB: For clarity and to re-emphasise, the "virtual cost" will be applied to BOTH the cost calculation for charging AND for discharging the battery._
 
 If you configure this number higher then more expensive plans will be selected which avoids charging and discharging your battery as much.
-The default is 0.5p (meaning an extra virtual cost of 1p per kWh to charge and discharge) but can be set to 0 if you want to turn this feature off.
+
 Note that the cycle cost will not be included in the cost predictions that Predbat produces such as the Predbat HTML plan or Apex charts,
 its just a cost taken into account by Predbat at the planning stage when the plan is calculated.<BR>
 _NB: Setting this to a non-zero value will increase your daily cost, but will reduce your home battery usage._
 
-Figures of around 0p-2p are recommended, the default is 0.5p per kWh.
+Figures of around 0p-2p are recommended, the default is 0p per kWh.
 
 **input_number.predbat_metric_battery_value_scaling** (_expert mode_) A percentage value that can be used to scale the value of the energy in the battery at the end of the plan.
 The battery value is accounted for in the optimisations at the lowest future import rate including charging and inverter losses.