diff --git a/docs/commandref.html b/docs/commandref.html
index 0cfea3bf9..e6ccf703e 100644
--- a/docs/commandref.html
+++ b/docs/commandref.html
@@ -107,9 +107,9 @@
M232
M232Counter
M232Voltage
- MSG
- MSGFile
- MSGMail
+ MSG
+ MSGFile
+ MSGMail
NetIO230B
OREGON
OWFS
@@ -143,6 +143,8 @@
WS3600
X10
xxLG7000
+ ZWDongle
+ ZWave
@@ -8505,6 +8507,292 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK.
You need to define an RFXtrx433
+
+ZWDongle
+
+ This module serves a ZWave dongle, which is attached via USB or TCP/IP, and
+ enables the use of ZWave devices (see also the ZWave
+ module). It was tested wit a Goodway WD6001, but since the protocol is
+ standardized, it should work with other devices too. A notable exception is
+ the USB device from Merten.
+
+
+ Define
+
+ define <name> ZWDongle <device>
+
+
+ Upon initial connection the module will get the homeId of the attached
+ device. Since the DevIo module is used to open the device, you can also use
+ devices connected via TCP/IP. See this paragraph on
+ device naming details.
+
+ Example:
+
+ define zwdongle_1 ZWDongle /dev/cu.PL2303-000014FA@115200
+
+
+
+
+
+ Set
+
+
+ - addNode [on|off]
+ Activate (or deactivate) inclusion mode. The controller (i.e. the dongle)
+ will accept inclusion (i.e. pairing/learning) requests only while in this
+ mode. After activating inclusion mode usually you have to press a switch
+ three times within 1.5 seconds on the node to be included into the network
+ of the controller. If autocreate is active, a fhem device will be created
+ after inclusion.
+
+ - removeNode [on|off]
+ Activate (or deactivate) exclusion mode. Note: the corresponding fhem
+ device have to be deleted manually.
+
+ - createNode id
+ Request the class information for the specified node, and create a fhem
+ device upon reception of the answer. Used for previously included nodes,
+ see the nodeList get command below.
+
+
+
+
+
+ Get
+
+ - nodeList
+ return the list of included nodeIds. Can be used to recreate fhem-nodes
+ with the createNode command.
+
+ - homeId
+ return the six hex-digit homeId of the controller.
+
+ - caps, ctrlCaps, version
+ return different controller specific information. Needed by developers only.
+
+ - nodeInfo
+ return node specific information. Needed by developers only.
+
+
+ - raw
+ Send raw data to the controller. Developer only.
+
+
+
+
+ Attributes
+
+
+
+
+ Generated events:
+
+ - ZW_ADD_NODE_TO_NETWORK [learnReady|nodeFound|controller|done|failed]
+
- ZW_REMOVE_NODE_TO_NETWORK [learnReady|nodeFound|slave|controller|done|failed]
+
- UNDEFINED ZWave_${type6}_$id ZWave $homeId $id $classes"
+
+
+
+
+
+
+ZWave
+
+ This module is used to control ZWave devices via FHEM, see www.z-wave.com on details for this device family.
+ This module is a client of the ZWDongle module, which
+ is directly attached to the controller via USB or TCP/IP.
+
+
+ Define
+
+ define <name> ZWave <homeId> <id> [classes]
+
+
+ <homeId> is the homeId of the controller node, and id is the id of the
+ slave node in the network of this controller.
+ 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.
+
+ Example:
+
+ define lamp ZWave 00ce2074 9
+ attr lamp classes SWITCH_BINARY BASIC MANUFACTURER_SPECIFIC VERSION SWITCH_ALL ASSOCIATION METER CONFIGURATION ALARM
+
+
+
+
+ Note: the sets/gets/generated events of a gven node depend on the classes
+ supported by this node. If a node supports 3 classes, then the union of
+ these sets/gets/events will be available for this node.
+ Commands for battery operated nodes will be queues internally, and sent when
+ the node sends a message. Answer to get commands appear then as events, the
+ corresponding readings will be updated.
+
+
+
+ Set
+
+
+
Class BASIC
+ - basicValue value
+ Send value (0-255) to this device. The interpretation is device dependent,
+ e.g. for a SWITCH_BINARY device 0 is off and anything else is on.
+
+
Class SWITCH_BINARY
+ - on
+ switch the device on
+ - off
+ switch the device off
+ - reportOn,reportOff
+ activate/deactivate the reporting of device state changes to the association group.
+
+
Class CONFIGURATION
+ - configByte cfgAddress 8bitValue
+ configWord cfgAddress 16bitValue
+ configLong cfgAddress 32bitValue
+ Send a configuration value for the parameter cfgAddress. cfgAddress and
+ value is node specific.
+ - configDefault cfgAddress
+ Reset the configuration parameter for the cfgAddress parameter to its default value.
+ See the device documentation to determine this value.
+
+
Class WAKE_UP
+ - wakeupInterval value
+ Set the wakeup interval of battery operated devices to the given value in
+ seconds. Upon wakeup the device sends a wakeup notification.
+
+
Class ASSOCIATION
+ - associationAdd groupId nodeId ...
+ Add the specified list of nodeIds to the assotion group groupId.
+ Note: upon creating a fhem-device for the first time fhem will automatically
+ add the controller to the first association group of the node corresponding
+ to the fhem device, i.e it issues a "set name associationAdd 1 controllerNodeId"
+
+ - associationDel groupId nodeId ...
+ Remove the specified list of nodeIds from the assotion group groupId.
+
+
+
+
+
+ Get
+
+
+
Class BASIC
+ - basicStatus
+ return the status of the node as basicReport:XY. The value (XY) depends on
+ the node, e.g a SWITCH_BINARY device report 00 for off and FF (255) for on.
+
+
Class SWITCH_BINARY
+ - swbStatus
+ return the status of the node, as state:on or state:off.
+
+
Class SENSOR_BINARY
+ - sbStatus
+ return the status of the node, as state:open or state:closed.
+
+
Class CONFIGURATION
+ - config cfgAddress
+ return the value of the configuration parameter cfgAddress. The value is
+ device specific.
+
+
Class ALARM
+ - alarm alarmId
+ return the value for alarmId. The value is device specific.
+
+
Class BATTERY
+ - battery
+ return the charge of the battery in %, as battery:value %
+
+
Class WAKE_UP
+ - wakeupInterval
+ return the wakeup interval in seconds, in the form
+ wakeupReport:interval:seconds target:id
+
+
Class ASSOCIATION
+ - association groupId
+ return the list of nodeIds in the association group groupId in the form:
+ assocGroup_X:Max:Y Nodes:id,id...
+
+
Class VERSION
+ - version
+ return the version information of this node in the form:
+ Lib:A Prot:x.y App:a.b
+
+
+
+
+
+ Attributes
+
+
+
+
+ Generated events:
+
+
+
Class BASIC
+ - basicReport:XY
+
+
Class SWITCH_BINARY
+ - state:on
+
- state:off
+
+
Class SENSOR_BINARY
+ - state:open
+
- state:closed
+
+
Class METER
+ - power:val [kWh|kVAh|W|pulseCount]
+
- gas:val [m3|feet3|pulseCount]
+
- water:val [m3|feet3|USgallons|pulseCount]
+
+
Class CONFIGURATION
+ - config_X:Y
+
+
Class ALARM
+ - alarm_type_X:level Y
+
+
Class BATTERY
+ - battery:chargelevel %
+
+
Class WAKE_UP
+ - wakeup:notification
+
- wakeupReport:interval:X target:Y
+
+
Class ASSOCIATION
+ - assocGroup_X:Max:Y Nodes:A,B,...
+
+
Class VERSION
+ - Lib:A Prot:x.y App:a.b
+
+
+
+
+
+
weblink
@@ -10134,8 +10422,9 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK.
You need to define an RFXtrx433
Log events to <filename>. The log format is
YYYY:MM:DD_HH:MM:SS <device> <event>
- The regexp will be checked against the (complete!) device name
- or against the (complete!) devicename:event combination.
+ The regexp will be checked against the device name
+ 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).