"sudo cpan
+ If you need this module, you can install it e.g. with "sudo cpan
Device::SerialPort". There are also precompiled debian packages
(libdevice-serialport-perl), and this module is already installed on OSX
10.6. If you cannot install it, you then take a look at the @directio
option in the commandref.html as a last resort.
- The default configuration will install fhem into /usr/bin,
- /usr/share/fhem and /var/log/fhem and /etc/fhem.cfg, according to the
- debian/ubuntu requirments. Edit the Makefile to change this.
+ The default configuration will install fhem into /opt/fhem, edit the
+ Makefile to change this. You can also start fhem directly from where you
+ unpacked it, installation is optional.
To install & start fhem type:
- make install-pgm2
- perl /usr/bin/fhem.pl /etc/fhem.cfg
+ make
+ cd /opt/fhem
+ perl fhem.pl fhem.cfg
+
+ After starting, the fhem logfile in the log directory should look like:
+ 2012.10.27 17:14:28 1: Including fhem.cfg
+ 2012.10.27 17:14:28 3: WEB: port 8083 opened
+ 2012.10.27 17:14:28 3: WEBphone: port 8084 opened
+ 2012.10.27 17:14:28 3: WEBtablet: port 8085 opened
+ 2012.10.27 17:14:28 1: Including /tmp/fhem.save
+ 2012.10.27 17:14:28 3: telnetPort: port 7072 opened
+ 2012.10.27 17:14:28 1: usb create starting
+ 2012.10.27 17:14:28 1: usb create end
+ 2012.10.27 17:14:28 2: SecurityCheck: ...
+ 2012.10.27 17:14:28 0: Server started (version Fhem 5.3 ...
+
+ The SecurityCheck warning tells you, that some of the fhem interfaces are
+ opened without a passwort. You should either set a password for each
+ device (see below), or set a global attribute to disable this message if
+ you are sure passwords are not needed.
- After starting, the logfile should look like:
- 2008.06.15 16:17:03 2: FHEMWEB port 8083 opened
- 2008.06.15 16:17:03 2: FHEMWEB port 8084 opened
- 2008.06.15 16:17:03 2: FHEMWEB port 8085 opened
- 2008.06.15 16:17:03 0: Server started (version ...)
@@ -79,26 +94,30 @@
http://fhem-host:8085/fhem if
you are using a tablet like the iPad.
- In the default configuration, fhem will look for USB attached FHZ, CUL
- and TCM devices on startup (unix/OSX only) and will create
- appropriate fhem devices.
+ Note: On the FritzBox the default configuration enables password
+ checking on all interfaces: The username is ignored, and the passwort is
+ checked against the FritzBox password.
- On linux (esp. FB7390) it will even try to
- flash the unflashed CUL, if it is attached at startup. See the usb and
+
+ On linux (esp. FB7390) fhem will try to flash an unflashed CUL, if it is
+ attached at startup. See the usb and CULflash commands for details, and
- check the "unsorted" room in FHEMWEB for the newly created
- devices. Note that switching a CUL to HomeMatic mode is still has to be
- done manually. Only one device is flashed per fhem-startup.
+ check the "unsorted" room in FHEMWEB for the newly created devices. Note
+ that switching a CUL to HomeMatic mode is still has to be done manually.
+
- For doing it manually (or if fhem failed to discover your device):
- Attach the USB device (CUL, FHZ1000PC/FHZ1300, TUL, EUL, etc) to your
- computer, and look for the corresponding device in the /dev
+ For defining USB Input devices manually (or if fhem failed to discover
+ your device): Attach the USB device (CUL, FHZ1000PC/FHZ1300, TUL, EUL,
+ etc) to your computer, and look for the corresponding device in the /dev
directory. For CUL a file named
- /dev/ttyACM* will be created under
- Linux and /dev/cu.usbmodem* under OS X. Note the exact name of the device.
- Define it for fhem (by typing it in the "Fhem cmd" input field in the
- browser):
+ /dev/ttyACM* will be created under Linux and /dev/cu.usbmodem* under OS
+ X. Note the exact name of the device. Define it for fhem (by typing it
+ in the "Fhem cmd" input field in the browser):
+
define CUL1 CUL /dev/ttyACM0@9600 1234
You can find details about CUL define parameters FHZ with
slightly different parameters:
define FHZ1 FHZ /dev/ttyUSB0
- For the FHZ on OSX you need to install the ftdi driver first from
- http://www.ftdichip.com/Drivers/VCP.htm, the device name will be
- /dev/cu.usbserial-xxxxxxxx.
-
-
Notes:
- Don't forget to type "save" in the "Fhem cmd" input field of the
browser after defining a device or setting its attribute. Otherwise
the changes will disappear after the next start.
+
- Execute commands by typing enter in the FHEMWEB input line.
+ Clicking on the save button won't execute your command.
- The CUL is arriving without a firmware. You can flash it via the
CULflash command, if the
dfu-programmer is installed. dfu-programmer is part of the FB7390 image.
@@ -127,11 +142,11 @@
Configuring transmitter devices (i.e. sensors)
- 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 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
+ Many Radio devices will be created automatically in the default
+ configuration, due to the enabled
+ autocreate instance. This will automatically create fhem devices upon
+ reception 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:
@@ -140,10 +155,9 @@
rename FHT_1234 fht.kitchen