From 89707bdf42cc55f5d48349a5aa0bb350326995bb Mon Sep 17 00:00:00 2001 From: rudolfkoenig <> Date: Mon, 3 Oct 2011 18:32:17 +0000 Subject: [PATCH] Removed the advice for report1 git-svn-id: https://svn.fhem.de/fhem/trunk@1043 2b470e98-0d58-463d-a4d8-8e2adae1ed80 --- fhem/docs/commandref.html | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/fhem/docs/commandref.html b/fhem/docs/commandref.html index 6364b5602..d880931d6 100644 --- a/fhem/docs/commandref.html +++ b/fhem/docs/commandref.html @@ -1565,10 +1565,9 @@ A line ending with \ will be concatenated with the next one, so long lines 24:00 means off.

-
  • As the FHT stops sending the values every 5-10 - days, it is adviseable to schedule following command regularly:
    - define fht_report at +*06:00:00 - set <name> report1 255 report2 255 +
  • To synchronize the FHT time and to "wake" muted FHTs it is adviseable + to schedule following command:
    + define fht_sync at +*3:30 set TYPE=FHT time

  • report1 with parameter 255 requests all settings for @@ -1587,6 +1586,9 @@ A line ending with \ will be concatenated with the next one, so long lines appropriate by the FHT.

    + Note: This command generates a lot of RF traffic, which can + lead to further problems, especially if the reception is not clear. +

  • report2 with parameter 255 requests the following settings to be reported: day-temp night-temp windowopen-temp @@ -6916,8 +6918,8 @@ href="http://www.elv.de/output/controller.aspx?cid=74&detail=10&detail2=29870">U Examples:
    -    # "Reset" the FHT80 if we do not receive any message for 15 Minutes
    -    define w watchdog FHT80 00:15:00 SAME set FHT80 refreshvalues
    +    # Talk to the FHT80 if we do not receive any message for 15 Minutes
    +    define w watchdog FHT80 00:15:00 SAME set FHT80 time
         # Shout if the HMS100-FIT is not alive
         define w watchdog HMS100-FIT 01:00:00 SAME "alarm-fit.sh"