diff --git a/fhem/docs/commandref.html b/fhem/docs/commandref.html
index 395adff7b..c2a4923a8 100644
--- a/fhem/docs/commandref.html
+++ b/fhem/docs/commandref.html
@@ -406,7 +406,7 @@ A line ending with \ will be concatenated with the next one, so long lines
of the standardized readings updating mechanism in fhem.pl. Check the modules
Attributes list if you want to know if it is supporting it.
-
+
define lamp1 EIB 0/10/01 0/10/02
set lamp1 on g2 (will send "on" to 0/10/02)
define <name> MSGFile <filename>
set myMsg send myMail
set myMail clear
latitude
and longitude
are decimal numbers which give the position on earth for which the twilight states shall be calculated.define myTwilight Twilight 49.962529 10.324845 3 676757 @@ -5260,7 +5264,7 @@ To send the data, both send or write could be used.
Get
get <name> <reading>
light | the current virtual daylight value |
ss | time of sunset |
ss_civil | time of civil sunset |
ss_nautic | time of nautic sunset |
ss_astro | time of astro sunset |
ss_astro | time of astro sunset |
set <name> <state> [<time in ms>]
get <name> <type>
-
+
You need to have the perl module GD
installed. This module is most likely not
available for small systems like Fritz!Box.
@@ -6026,7 +6030,7 @@ Attributes:
size
. The background is black if no usable JPEG picture can be found. Next the
script in the layout definition is used to superimpose items on
the background.- + You can directly access the URL of the JPEG picture in your browser. Reload the page to see how it works.
- + The media RSS feed advertises to refresh after 1 minute (ttl). Some photo frames ignore it and use their preset refresh rate. Go for a photo frame with an adjustable refresh rate (e.g every 5 seconds) if you have the choice!
@@ -6091,7 +6095,7 @@ Attributes:
attr FrameRSS bg /usr/share/pictures
attr FrameRSS tmin 10
-
+
-# Do not use any long IDs for any devices: +# Do not use any long IDs for any devices: attr RFXCOMUSB longids 0 -# Use any long IDs for all devices (this is default): +# Use any long IDs for all devices (this is default): attr RFXCOMUSB longids 1 -# Use longids for BTHR918N devices. +# Use longids for BTHR918N devices. # Will generate devices names like BTHR918N_f3. attr RFXCOMUSB longids BTHR918N -# Use longids for TX3_T and TX3_H devices. +# Use longids for TX3_T and TX3_H devices. # Will generate devices names like TX3_T_07, TX3_T_01 ,TX3_H_07. attr RFXCOMUSB longids TX3_T,TX3_H
# # Webcam credentials - # + # $credentials{<name_cam1>}{username} = "<your_username>"; $credentials{<name_cam1>}{password} = "<your_password>"; $credentials{<name_cam2>}{username} = "<your_username>"; $credentials{<name_cam2>}{password} = "<your_password>"; ... -+ Replace
<name_cam1>
respectively <name_cam2>
with the names of your defined ip-cams and <your_username>
respectively
<your_password>
with your credentials (all without the brackets
@@ -8322,14 +8326,14 @@ href="http://www.elv.de/output/controller.aspx?cid=74&detail=10&detail2=29870">U
- This module is for the RFXCOM RFXtrx433 USB based 433 Mhz RF transmitters.
+ This module is for the RFXCOM RFXtrx433 USB based 433 Mhz RF transmitters.
This USB based transmitter is able to receive and transmit many protocols like Oregon Scientific weather sensors, X10 security and lighting devices, ARC ((address code wheels) HomeEasy, KlikAanKlikUit, ByeByeStandBy, Intertechno, ELRO,
AB600, Duewi, DomiaLite, COCO) and others. Currently the following parser modules are implemented:
Examples: -# Do not use any long IDs for any devices (this is default): +# Do not use any long IDs for any devices (this is default): attr RFXCOMUSB longids 0 # Use long IDs for all devices: attr RFXCOMUSB longids 1 -# Use longids for BTHR918N devices. +# Use longids for BTHR918N devices. # Will generate devices names like BTHR918N_f3. attr RFXTRXUSB longids BTHR918N -# Use longids for TX3_T and TX3_H devices. +# Use longids for TX3_T and TX3_H devices. # Will generate devices names like TX3_T_07, TX3_T_01 ,TX3_H_07. attr RFXTRXUSB longids TX3_T,TX3_H @@ -8436,7 +8440,7 @@ attr RFXTRXUSB longids TX3_T,TX3_H <deviceid2>
<devicelog2>
@@ -8544,7 +8548,7 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK. You need to define an RFXtrx433 where value is one of:off - on + on dim # only for X10, KOPPLA bright # only for X10, KOPPLA all_off # only for X10, ARC, EMW200, AC, HOMEEASY, ANSLUT @@ -8573,7 +8577,7 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK.
@@ -8593,7 +8597,7 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK. You need to define an RFXtrx433 "THGR810", "RTGR328", "THGR328", - "WTGR800_T" (for temperature of WTGR800), + "WTGR800_T" (for temperature of WTGR800), "THGR918" (for THGR918, THGRN228, THGN500), "TFATS34C" (for TFA TS34C), "BTHR918", @@ -8831,7 +8835,7 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK. You need to define an RFXtrx433 classes is a hex-list of ZWave device classes. This argument is usually specified by autocreate when creating a device. If you wish to manually create a device, use the classes attribute instead, see below for details. - Defining a ZWave device the first time is usually done by autocreate. + Defining a ZWave device the first time is usually done by autocreate. Example:
You need to define an RFXtrx433 can group these weblinks by putting them into rooms. If you convert the current logfile to a weblink, it will always refer to the current file, even if its name changes regularly (and not the one you - originally specified). + originally specified). You need to define an RFXtrx433 - Set + Set set <name> rereadicons
@@ -9228,7 +9232,7 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK. You need to define an RFXtrx433 /data/Homeautomation/fhem/FHEM/FS20.on.png - + You need to define an RFXtrx433 FLOORPLAN
- Step-by-step setup guides are available in - english and + Step-by-step setup guides are available in + english and german. @@ -9499,7 +9503,7 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK. You need to define an RFXtrx433 define Groundfloor FLOORPLAN fp_Groundfloor.png - @@ -9525,7 +9529,7 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK. You need to define an RFXtrx433
|
attr Groundfloor fp_noMenu 1
attr Groundfloor commandfield 1
define <name> dewpoint dewpoint <devicename-regex> [<temp_name> <hum_name> <new_name>]
- # Compute the dewpoint for the temperature/humidity + # Compute the dewpoint for the temperature/humidity # events of the temp1 device and generate reading dewpoint. define dew_temp1 dewpoint dewpoint temp1 define dew_temp1 dewpoint dewpoint temp1 temperature humidity dewpoint - # Compute the dewpoint for the temperature/humidity + # Compute the dewpoint for the temperature/humidity # events of all devices offering temperature and humidity # and generate reading dewpoint. define dew_all dewpoint dewpoint .* define dew_all dewpoint dewpoint .* temperature humidity dewpoint - # Compute the dewpoint for the temperature/humidity + # Compute the dewpoint for the temperature/humidity # events of the device Aussen_1 offering temperature and humidity # and insert is into STATE. define dew_state dewpoint dewpoint Aussen_1 T H D - # Compute the dewpoint for the temperature/humidity + # Compute the dewpoint for the temperature/humidity # events of all devices offering temperature and humidity # and insert the result into the STATE. # Example STATE: "T: 10 H: 62.5" will change to @@ -10015,10 +10019,10 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK.
You need to define an RFXtrx433define <name> dewpoint fan <devicename-regex> <devicename-outside> <min-temp>
- # Generate event "fan: on" when dewpoint of Aussen_1 is first + # Generate event "fan: on" when dewpoint of Aussen_1 is first # time lower than basement_tempsensor and outside temperature is >= 0 # and change it to "fan: off" is this condition changes. # Set a switch on/off (fan_switch) depending on the state. define dew_fan1 dewpoint fan basement_tempsensor Aussen_1 0 define dew_fan1_on notify basement_tempsensor.*fan:.*on set fan_switch on define dew_fan1_off notify basement_tempsensor.*fan:.*off set fan_switch off - +@@ -10042,10 +10046,10 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK.
define <name> dewpoint alarm <devicename-regex> <devicename-reference> <diff-temp>
- # Using a wall temperature sensor (wallsensor) and a temp/hum sensor - # (roomsensor) to alarm if the temperature of the wall is lower than - # the dewpoint of the air. In this case the water of the air will + # Using a wall temperature sensor (wallsensor) and a temp/hum sensor + # (roomsensor) to alarm if the temperature of the wall is lower than + # the dewpoint of the air. In this case the water of the air will # condense on the wall because the wall is cold. # Set a switch on (alarm_siren) if alarm is on using notify. define dew_alarm1 dewpoint alarm roomsensor wallsensor 0 @@ -10063,11 +10067,11 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK.@@ -10534,7 +10538,7 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK.
You need to define an RFXtrx433 define roomsensor_alarm_off notify roomsensor.*fan:.*off set alarm_siren off # If you do not have a temperature sensor in/on the wall, you may also - # compare the rooms dewpoint to the temperature of the same or another - # inside sensor. Alarm is temperature is 5 degrees colder than the - # inside dewpointinside. + # compare the rooms dewpoint to the temperature of the same or another + # inside sensor. Alarm is temperature is 5 degrees colder than the + # inside dewpointinside. define dev_alarm2 dewpoint alarm roomsensor roomsensor 5 - +
YYYY:MM:DD_HH:MM:SS <device> <event>The regexp will be checked against the device name - devicename:event or timestamp:devicename:event combination. + devicename:event or timestamp:devicename:event combination. The regexp must match the complete string, not just a part of it.
<filename>
may contain %-wildcards of the
- POSIX strftime function of the underlying OS (see your strftime manual).
+ <filename>
may contain %-wildcards of the
+ POSIX strftime function of the underlying OS (see your strftime manual).
Common used wildcards are:
%d
day of month (01..31)%W
week number of year with Monday as first day of week (00..53)
%L
by the value of the global logdir attribute.%V
for ISO 8601 week numbers check if it is
- correctly supported by your system (%V may not be replaced, replaced by an
- empty string or by an incorrect ISO-8601 week number, especially
+ Before using %V
for ISO 8601 week numbers check if it is
+ correctly supported by your system (%V may not be replaced, replaced by an
+ empty string or by an incorrect ISO-8601 week number, especially
at the beginning of the year)
- If you use %V
you will also have to use %G
+ If you use %V
you will also have to use %G
instead of %Y for the year!