From 298f29d4a2a9f9a745944e4f1a2c9d087cfd2022 Mon Sep 17 00:00:00 2001 From: Samuel <40698384+samuel-esp@users.noreply.github.com> Date: Sun, 4 Aug 2024 22:07:05 +0200 Subject: [PATCH] added overlapping times explaination to docs --- README.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index a9f063c..079a167 100644 --- a/README.md +++ b/README.md @@ -281,6 +281,24 @@ Each time specification can be in one of two formats: `--
T::[+-]:`. +If you are using the first format (recurring specifications) it is important +to note that the downscaler can only interpret configurations within +a single day and cannot process intervals that stretch across two different days. +As a result, overlapping time intervals are not supported. + +In the expression `- :-: ` +the time range `:-:` should always have the end time later +than the start time (in 24-hour format) + +If you want to schedule downtime from 23:30 to 09:30 the following day, +a configuration like this would be incorrect: + +`DEFAULT_DOWNTIME="Mon-Fri 23:30-09:30 Europe/Berlin"` + +The correct configuration would be: + +`DEFAULT_DOWNTIME="Mon-Fri 23:30-24:00 Europe/Berlin,Mon-Fri 00:00-09:30 Europe/Berlin"` + ### Alternative Logic, Based on Periods Instead of strict uptimes or downtimes, you can chose time periods for @@ -301,7 +319,6 @@ day 19:00-20:00. DOWNSCALE_PERIOD="Mon-Sun 19:00-20:00 Europe/Berlin" ``` - ### Command Line Options Available command line options: