From c663f876d067f233ab1a863b5db306bce8d55744 Mon Sep 17 00:00:00 2001 From: rudolfkoenig <> Date: Thu, 18 Oct 2018 14:45:30 +0000 Subject: [PATCH] 90_at.pm: more doc for disabledForIntervals with date syntax (Forum #92194) git-svn-id: https://svn.fhem.de/fhem/trunk/fhem@17561 2b470e98-0d58-463d-a4d8-8e2adae1ed80 --- FHEM/90_at.pm | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/FHEM/90_at.pm b/FHEM/90_at.pm index 518b4b500..bde26a0e2 100644 --- a/FHEM/90_at.pm +++ b/FHEM/90_at.pm @@ -555,12 +555,15 @@ EOF but the next time will be computed.
-
  • disabledForIntervals HH:MM-HH:MM HH:MM-HH-MM...
    +
  • disabledForIntervals HH:MM-HH:MM HH:MM-HH:MM ...
    Space separated list of HH:MM or D@HH:MM tupels. If the current time is between the two time specifications, the current device is disabled. Instead of HH:MM you can also specify HH or HH:MM:SS. D is the day of - the week, with 0 indicating Sunday and 3 indicating Wednesday. To - specify an interval spawning midnight, you have to specify two + the week, with 0 indicating Sunday and 3 indicating Wednesday. + Specifying the day for the "from" part does _not_ specify it for the + "to" part, i.e. 1@00-24 will disable from monday to the end of the + week, but not on sunday (as 1@00 is greater than any time on sunday). + To specify an interval spawning midnight, you have to specify two intervals, e.g.: