define tul TUL eibd:<server address>[:<server port>] <physicaladdress>
FHEM => eibd => (any supported BCU i.e. TUL) => bus
FHEM => TPUART (i.e. TUL) => bus
The reason is mainly to make "eibd" expendable as it might not run on smaller embedded systems. So you can connect to the bus directly via TUL, which is a serial TPUART over USB.
eibd is of course:
http://www.auto.tuwien.ac.at/~mkoegler/index.php/eibd
> --
> To unsubscribe from this group, send email to
> fhem-users+...@googlegroups.com
Autocreate listens for the "global:UNDEFINED" event, which is triggered if the
modules ParseFn() returns "UNDEFINED" to Dispatch(). As far as I see this is
done by 10_EIB.pm correctly, i.e. autocreate for EIB devices should work.
On the "UNDEFINED" event autocreate creates a device by calling the modules
DefineFn with the parameters reported by the UNDEFINED event, then it creates
the corresponding FileLog. If autocreate "knows" that the device is a sensor,
then it also creates a Plot for the device. This is not yet the case for EIB
devices.
> Frage so nebenbei wie wird dabei eigentlich festgelegt welches Gerät
> die eins und welches die zwei bekommt?
Bitte somewhere in udev definieren:
/etc/udev/rules.d/50-udev.rules:
KERNEL=="ttyACM*", ATTRS{product}=="TPUART transparent", SYMLINK
+="tpuarttransparent"
dann in fhem.cfg z.B.:
define KNX TUL tul:/dev/tpuarttransparent 1.1.249
define Schlaf.Rollo EIB 8/0/7
attr Schlaf.Rollo IODev KNX
attr Schlaf.Rollo room Schlaf
Setzt natürlich vorraus, dass das TUL mit:
http://busware.de/tiki-download_file.php?fileId=54
geflashed wurde.