diff --git a/FHEM/00_CUL.pm b/FHEM/00_CUL.pm
index 0d19edd1e..748f53af3 100755
--- a/FHEM/00_CUL.pm
+++ b/FHEM/00_CUL.pm
@@ -790,7 +790,7 @@ CUL_Parse($$$$$)
} elsif($fn eq "E" && $len >= 11) { # CUL_EM / Native
;
} else {
- Log GetLogLevel($name,2), "CUL: unknown message $dmsg";
+ Log GetLogLevel($name,2), "$name: unknown message $dmsg";
return;
}
@@ -898,7 +898,7 @@ CUL_OpenDev($$)
$hash->{PARTIAL} = "";
- Log 3, "CUL opening CUL device $dev"
+ Log 3, "CUL opening $name device $dev"
if(!$reopen);
if($dev =~ m/^(.+):([0-9]+)$/) { # host:port
diff --git a/FHEM/92_FileLog.pm b/FHEM/92_FileLog.pm
index e525d8e43..433b77086 100755
--- a/FHEM/92_FileLog.pm
+++ b/FHEM/92_FileLog.pm
@@ -185,7 +185,7 @@ FileLog_Get($@)
my $linf = "$1/$inf" if($hash->{currentlogfile} =~ m,^(.*)/[^/]*$,o);
if(!-f $linf) {
$linf = $attr{$hash->{NAME}}{archivedir} . "/" . $inf;
- return "Error: File-not-found" if(!-f $linf);
+ return "Error: cannot access $linf" if(!-f $linf);
}
$inf = $linf;
}
diff --git a/docs/HOWTO.html b/docs/HOWTO.html
index 030c56ba8..191fcbf3c 100644
--- a/docs/HOWTO.html
+++ b/docs/HOWTO.html
@@ -1,4 +1,7 @@
-
+
+
+
+
FHEM Howto
-
@@ -86,36 +88,22 @@
The sample configuration file installed via "make install-pgm2" has
configured an autocreate
instance. This will automatically create fhem devices upon reception
- of a message form this device (typically a sensor like S300 or FHT).
- Just wait for a while, and re-check your browser for newly appeared
- devices. You can use rename to
- rename the automatically created device, e.g. type in the input field of
- the web frontend:
+ of a message from this device (typically a sensor like S300 or FHT).
+ Just wait for a while, watch the log and re-check your browser for newly
+ appeared devices. You can use
+ rename to rename the automatically created device, e.g. type in the
+ input field of the web frontend:
rename FHT_1234 fht.kitchen
-
- Configuring FS20 receivers
-
- Configure the FS20 device in
- fhem first with:
- define lamp1 FS20 1234 56
-
- Now press the button on the device for a while until its LED starts to
- blink. Click on the "on" link in the fhem window to send a command. The
- LED should terminate blinking, the device is programmed to housecode
- 1234, device code 56. You can also use the 4-base ELV notation.
- Now set the model attribute of the device:
- attr lamp1 model fs20st
-
- to get only the commands available for this device.
- Here is a complete list of models.
-
-
Misc. RF transmitters (FS20/EM/S300 etc.)
+ autocreate will create
+ automatically fhem FS20/EM/S300/HMS devices, the following description is
+ for doing it manually.
+
Wait a while, until the transmitter sent some data. In the logfile
(Browser window: "All together" -> Logs:Logfile:text) a line
will appear:
@@ -133,9 +121,37 @@
+
+ Configuring FS20 receivers
+
+ Configure the FS20 device in
+ fhem first with:
+ define lamp1 FS20 1234 56
+
+ Now press the button on the device for a while until its LED starts to
+ blink. Click on the "on" link in the fhem window to send a command. The
+ LED should terminate blinking, the device is programmed to housecode
+ 1234, device code 56. You can also use the 4-base ELV notation.
+ Now set the model attribute of the device:
+ attr lamp1 model fs20st
+
+ to get only the commands available for this device.
+ Here is a complete list of models.
+
+
+
Configuring FHT devices
+ Note: Creating a fhem FHT device automatically or manually does
+ not imply that the CUL or the FHZ is paired with it. For this purpose you
+ have to set the FHT to accept new "Cent" devices, and send a command to
+ it (e.g. set fht.kitchen desired-temp 20)
+
+ autocreate will create
+ automatically FHT devices, the following description is for
+ doing it manually.
+
Wait for a while (2-5 mins) till the FHT is sending some signals. In the
logfile ("All together" -> Logs:LogFile:text) a line should
appear:
@@ -180,7 +196,7 @@
- FHEMWEB look and feel
+ FHEMWEB (pgm2) look and feel
It makes sense to group your devices into rooms by setting the room
attribute. FHEMWEB puts devices without a room attribute into the
@@ -203,7 +219,8 @@
Logging data
To log messages into files, define devices of the type FileLog. To log messages into a
+ href="commandref.html#FileLog">FileLog. Autocreate will create
+ logfiles for newly detected devices. To log messages into a
database, see the contrib/dblog directory in the fhem
distribution.
@@ -221,6 +238,9 @@
Plotting logs
+ Autocreate will create weblinks (i.e. plots) for newly detected devices.
+ The following section describes how to do it manually.
+
To convert a log into a plot in FHEMWEB, set the
logtype attribute of the
corresponding FileLog. Take a look at the available gnuplot files in the
@@ -242,8 +262,9 @@
installed and in your PATH), or via the builtin SVG module, in this case
your internet browser must support SVG. Firefox, opera and the
iPhone/Android borwser support SVG out of the box, Internet Explorer does
- it via the Adobe "SVG viewer" plugin. To use SVG graphics, set the plotmode attribute to SVG.
+ it via the Adobe "SVG viewer" plugin. SVG mode is the default, to change
+ it set the plotmode attribute to
+ gnuplot or gnuplot-scroll.
In order to look at historic data, you can either convert at the
archive entries to weblink in "plotmode=gnuplot" mode, or use the
diff --git a/docs/fhem.html b/docs/fhem.html
index 600155435..79539e0c4 100644
--- a/docs/fhem.html
+++ b/docs/fhem.html
@@ -132,7 +132,7 @@
one that won't encrypt the data.
- - reading an sending X10 events via the CM11 module (with access
+
- reading and sending X10 events via the CM11 module (with access
to a X10 computer interface)
@@ -195,8 +195,6 @@