Updated external content (Jenkins build 114)

_addons_bindings/dsmr/readme.md

@@ -21,12 +21,12 @@ When connecting this port from a serial port the data can be read out.
 This binding reads the P1-port of the Dutch Smart Meters that comply to NTA8130, DSMR v2.1, DSMR v2.2, DSMR v3.0, DSMR v4.0, DSMR v4.04, and DSMR 5.0.
 Although DSMR v4.2 is not an official specification, the binding has support for this version.
 
-If you are not living in the Netherlands but do want to read a meter please have look at the [IEC-62056-21 Meter Binding](https://github.com/openhab/openhab1-addons/wiki/IEC-62056---21-Meter-Binding).
+If you are not living in the Netherlands but do want to read a meter please have look at the [SmartMeter Binding](https://www.openhab.org/addons/bindings/smartmeter).
 Because the Dutch Meter standard is based on the IEC-62056-21 standard it might be desirable to build support for other country metering systems based on that standard in this binding.
 
 ## Serial Port Configuration
 
-The P1-port is a serial port. To configure the serial port within openHAB see the general documentation about serial port configuration: [/docs/administration/serial.html](/docs/administration/serial.html)
+The P1-port is a serial port. To configure the serial port within openHAB see the [general documentation about serial port configuration](/docs/administration/serial.html).
 
 ## Supported Things
 

_addons_bindings/mqtt.generic/readme.md

@@ -1,9 +1,9 @@
 ---
 id: mqtt.generic
-label: MQTT Thing
-title: MQTT Thing - Bindings
+label: MQTT Generic Thing
+title: MQTT Generic Thing - Bindings
 type: binding
-description: "MQTT is a machine-to-machine (M2M)/'Internet of Things' connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport."
+description: "> MQTT is a machine-to-machine (M2M)/'Internet of Things' connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport."
 since: 2x
 logo: images/addons/mqtt.generic.png
 install: manual
@@ -13,13 +13,13 @@ install: manual
 
 {% include base.html %}
 
-# MQTT Thing Binding
+# MQTT Generic Thing Binding
 
-    MQTT is a machine-to-machine (M2M)/"Internet of Things" connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport.
+> MQTT is a machine-to-machine (M2M)/"Internet of Things" connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport.
 
 This binding allows to link MQTT topics to Things.
 
-## Supported Thing
+## Supported Things
 
 The MQTT [Homie convention](https://homieiot.github.io/) version 3.x is supported by this binding.
 It allows to automatically discover devices that follow the "Homie" convention and present them as Things.
@@ -233,15 +233,15 @@ Here are a few examples:
 demo.Things:
 
 ```xtend
-Bridge mqtt:broker:myUnsecureBroker [ host="192.168.0.42",secure="OFF" ]
+Bridge mqtt:broker:myUnsecureBroker [ host="192.168.0.42", secure=false ]
 {
     Thing mqtt:topic:mything {
     Channels:
-        Type switch : lamp "Kitchen Lamp" [ mqttstate="lamp/enabled", mqttcommand="lamp/enabled/set" ]
-        Type switch : fancylamp "Fancy Lamp" [ mqttstate="fancy/lamp/state", mqttcommand="fancy/lamp/command", on="i-am-on", off="i-am-off" ]
-        Type string : alarmpanel "Alarm system" [ mqttstate="alarm/panel/state", mqttcommand="alarm/panel/set", allowedStates="ARMED_HOME,ARMED_AWAY,UNARMED" ]
-        Type color : lampcolor "Kitchen Lamp color" [ mqttstate="lamp/color", mqttcommand="lamp/color/set", rgb=true ]
-        Type dimmer : blind "Blind" [ mqttstate="blind/state", mqttcommand="blind/set", min=0, max=5, step=1 ]
+        Type switch : lamp "Kitchen Lamp" [ stateTopic="lamp/enabled", commandTopic="lamp/enabled/set" ]
+        Type switch : fancylamp "Fancy Lamp" [ stateTopic="fancy/lamp/state", commandTopic="fancy/lamp/command", on="i-am-on", off="i-am-off" ]
+        Type string : alarmpanel "Alarm system" [ stateTopic="alarm/panel/state", commandTopic="alarm/panel/set", allowedStates="ARMED_HOME,ARMED_AWAY,UNARMED" ]
+        Type color : lampcolor "Kitchen Lamp color" [ stateTopic="lamp/color", commandTopic="lamp/color/set", rgb=true ]
+        Type dimmer : blind "Blind" [ stateTopic="blind/state", commandTopic="blind/set", min=0, max=5, step=1 ]
     }
 }
 ```

_addons_bindings/mqtt/readme.md

@@ -3,7 +3,7 @@ id: mqtt
 label: MQTT
 title: MQTT - Bindings
 type: binding
-description: "MQTT is a machine-to-machine (M2M)/'Internet of Things' connectivity protocol."
+description: "> MQTT is a machine-to-machine (M2M)/'Internet of Things' connectivity protocol."
 since: 2x
 logo: images/addons/mqtt.png
 install: auto
@@ -15,14 +15,18 @@ install: auto
 
 # MQTT Binding
 
-    MQTT is a machine-to-machine (M2M)/"Internet of Things" connectivity protocol.
-    It was designed as an extremely lightweight publish/subscribe messaging transport.
+> MQTT is a machine-to-machine (M2M)/"Internet of Things" connectivity protocol.
+> It was designed as an extremely lightweight publish/subscribe messaging transport.
 
 MQTT is a server/client architecture.
 A server, also called broker is not provided within this binding,
 but it allows to detect running brokers and to manage connections.
 The hereby configured broker connections make it possible to link MQTT topics to Things and Channels.
 
+It has the following extensions:
+
+<!--list-subs-->
+
 ## Supported Bridges
 
 * Broker: This bridge represents a MQTT Broker connection, configured and managed by this binding.
@@ -93,11 +97,11 @@ in [Java MessageDigest Algorithms](https://docs.oracle.com/javase/9/docs/specs/s
 `mqttConnections.things`:
 
 ```xtend
-mqtt:broker:mySecureBroker [ host="192.168.0.41",secure="ON", certificatepin=true, publickeypin=true ]
-mqtt:broker:myUnsecureBroker [ host="192.168.0.42",secure="OFF" ]
+mqtt:broker:mySecureBroker [ host="192.168.0.41", secure=true, certificatepin=true, publickeypin=true ]
+mqtt:broker:myUnsecureBroker [ host="192.168.0.42",secure=false ]
 
-mqtt:broker:myAuthentificatedBroker [ host="192.168.0.43", username="user", password="password" ]
+mqtt:broker:myAuthentificatedBroker [ host="192.168.0.43", secure=true, username="user", password="password" ]
 
-mqtt:broker:pinToPublicKey [ host="192.168.0.44", publickeypin=true, publickey="SHA-256:9a6f30e67ae9723579da2575c35daf7da3b370b04ac0bde031f5e1f5e4617eb8" ]
+mqtt:broker:pinToPublicKey [ host="192.168.0.44", secure=true, publickeypin=true, publickey="SHA-256:9a6f30e67ae9723579da2575c35daf7da3b370b04ac0bde031f5e1f5e4617eb8" ]
 
-```
+```

_addons_bindings/samsungtv/readme.md

@@ -30,7 +30,7 @@ Tested TV models:
 | UE46D5700 | PARTIAL | Supports at my home only commands via the fake remote, no discovery                                              |
 | UE40F6500 | OK      | All channels except `colorTemperature`, `programTitle` and `channelName` are working                             |
 | LE40D579  | PARTIAL | Supported channels: `volume`, `mute`, `sourceName`, `channel`, `programTitle`, `channelName`, `keyCode`, `power` |
-
+| LE40C650 | PARTIAL | Supports channels: `volume`, `mute`, `brightness`, `contrast`, `colorTemperature`, `channel`, `keyCode`, `power` (only power off, unable to power on) |
 
 ## Discovery
 

_addons_bindings/withings1/readme.md

@@ -6,6 +6,7 @@ type: binding
 description: "The Withings binding allows openHAB to synchronize data from the official"
 source: https://github.com/openhab/openhab1-addons/blob/master/bundles/binding/org.openhab.binding.withings/README.md
 since: 1x
+logo: images/addons/withings.png
 install: manual
 ---
 

_addons_bindings/zigbee/readme.md

@@ -212,8 +212,9 @@ When things don't appear to be working as expected you should check the logs to
 ```
 log:set debug org.openhab.binding.zigbee
 log:set debug com.zsmartsystems.zigbee
+log:set info com.zsmartsystems.zigbee.dongle.ember.internal.ash
 ```
 
-This will log data into the standard openhab.log file.
+This will log data into the standard openhab.log file. There is an [online log viewer](https://www.cd-jackson.com/index.php/openhab/zigbee-log-viewer) available for viewing the logs.
 
 Note that logs can only show what is happening at a high level - it can't show all data exchanges between the device and the coordinator - just what the coordinator sends to the binding. For this reason it can be difficult to debug issues where devices are not joining the network, or other low level issues need resolving. In such cases a network sniffer log is required, which requires additional hardware and software.

_addons_bindings/zwave/doc/reitz/duw064374_0_0.md

@@ -8,6 +8,11 @@ title: Duewi ZW-ZS-3500 - ZWave
 # Duewi ZW-ZS-3500 Schuko Plug Switch
 This describes the Z-Wave device *Duewi ZW-ZS-3500*, manufactured by *Reitz-Group.de* with the thing type UID of ```reitz_duw064374_00_000```.
 
+The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there.
+
+![Duewi ZW-ZS-3500 product image](https://www.cd-jackson.com/zwave_device_uploads/623/623_default.jpg)
+
+
 The Duewi ZW-ZS-3500 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers.  This device is also able to participate in the routing of data between other devices in the mesh network.
 
 ## Overview

_addons_bindings/zwave/doc/tkb/tz68_0_0.md

@@ -104,7 +104,14 @@ This parameter has the configuration ID ```switchall_mode``` and is of type ```I
 
 Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
 
-The device does not support associations.
+The TZ68 supports 1 association group.
+
+### Group 1: Group1
+
+Association group info report command class Profile:General lifeline ( Profile MSB=0,Profile LSB=1) Association group name report command class Group 1:lifeline
+
+Association group 1 supports 5 nodes.
+
 ## Technical Information
 
 ### Endpoints
@@ -119,11 +126,13 @@ The device does not support associations.
 | COMMAND_CLASS_SWITCH_ALL_V1| |
 | COMMAND_CLASS_CONFIGURATION_V1| |
 | COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
+| COMMAND_CLASS_ASSOCIATION_V1| |
 | COMMAND_CLASS_VERSION_V1| |
 
 ### Documentation Links
 
 * [User Manual](https://www.cd-jackson.com/zwave_device_uploads/159/TKB-TZ68-E.pdf)
+* [User Manual](https://www.cd-jackson.com/zwave_device_uploads/159/TZ68-User-Manual.pdf)
 
 ---
 

_addons_bindings/zwave/doc/zooz/zse09_0_0.md

@@ -19,20 +19,86 @@ The ZSE09 does not permanently listen for messages sent from the controller - it
 
 ## Overview
 
+WELL DONE!
+
+You have picked the finest solution for your smart home, congratulations!
+
+Now it's time to enjoy these great features of your new Mini Sensor:
+
+  * Accurate motion and light level detection
+  * Wireless notifications and low battery alerts (when included to a Z-Wave gateway controller) - Custom automation scenarios based on both light and motion triggers (advanced configuration required)
+  * Adjustable sensitivity levels for motion detection to fit your needs
+  * Ultra small and simple design
+  * Z-Wave Plus with improved 500 chip for faster and safer wireless communication
+  * Flexible and quick installation
+
+**SPECIFICATIONS**
+
+  * Model Number: ZSE09
+  * Z-Wave Signal Frequency: 908.42 MHz
+  * Power: 1 CR123A battery (included)
+  * Power Consumption: 0.15W
+  * Operating Temperature: 32 – 104 F
+  * Motion detection: Up to 20 feet
+  * Range: Up to 100 feet line of sight
+  * Installation and Use: Indoor only
+  * Dimensions: 1.9” x 1.8”
+
+Weight: 1⁄2 oz
+
+Z-WAVE COMMAND CLASSES
+
+This device requires the following command classes to be supported and recognized by your Z-Wave controller:
+
+ZSE09
+
+ Z-Wave Plus Certified Device
+
+COMMAND\_CLASS\_ZWAVEPLUS\_INFO (V2) COMMAND\_CLASS\_VERSION (V2) COMMAND\_CLASS\_MANUFACTURER\_SPECIFIC (V2) COMMAND\_CLASS\_DEVICE\_RESET\_LOCALLY (V1) COMMAND\_CLASS\_POWERLEVEL (V1) COMMAND\_CLASS\_BATTERY (V1) COMMAND\_CLASS\_ASSOCIATION (V2) COMMAND\_CLASS\_ASSOCIATION\_GRP\_INFO (V1) COMMAND\_CLASS\_WAKE\_UP (V2) COMMAND\_CLASS_NOTIFICATION (V4)
+
+NOTIFICATION_REPORT
+
+NOTIFICATION\_TYPE\_HOME\_SECURITY NOTIFICATION\_EVENT\_HOME\_SECURITY\_MOTION\_DETECTION\_UNKNOWN\_LOCATION NOTIFICATION\_EVENT\_HOME\_SECURITY\_NO_EVENT
+
+COMMAND\_CLASS\_SENSOR\_BINARY (V2) SENSOR\_BINARY\_REPORT SENSOR\_MOTION
+
+COMMAND\_CLASS\_CONFIGURATION (V1) COMMAND\_CLASS\_SENSOR_MULTILEVEL (V7)
+
+### Inclusion Information
+
+  1. Bring the Mini Sensor within direct range of your controller
+  2. Carefully turn and lift the cover of your Mini Sensor to access the battery
+  3. Remove the plastic pull-tab from the battery slot. The LED indicator will blink slowly
+  4. Put your Z-Wave controller into inclusion mode
+  5. Press and release the Z-Wave button on the Mini Sensor 3 TIMES quickly. The LED indicator will flash quickly
+
+### Exclusion Information
+
+  1. Make sure the Mini Sensor is powered on and located within direct range of your Z-Wave gateway controller
+  2. Put your Z-Wave controller into exclusion mode
+  3. Press and release the Z-Wave button 3 TIMES quickly. The LED indicator will flash quickly
+  4. The Mini Sensor should disappear from your controller's device list
+
 ### Wakeup Information
 
 The ZSE09 does not permanently listen for messages sent from the controller - it will periodically wake up automatically to check if the controller has messages to send, but will sleep most of the time to conserve battery life. The wakeup period can be configured in the user interface - it is advisable not to make this too short as it will impact battery life - a reasonable compromise is 1 hour.
 
 The wakeup period does not impact the devices ability to report events or sensor data. The device can be manually woken with a button press on the device as described below - note that triggering a device to send an event is not the same as a wakeup notification, and this will not allow the controller to communicate with the device.
 
+
+WAKE-UP MODE
+
+If you change settings and parameters for the sensor, you may need to wake it up manually for the changes to be recorded. Press and release the Z-Wave button ONCE to wake the device up. The LED indicator will flash ONCE.
+
+The sensor’s wake-up interval is set to 12 hours by default to save battery life. Though not recommended, you can change the wake-up interval using your controller’s advanced settings if available. Minimum value: 300s (5 minutes), maximum value: 16,777,200s (around 194 days). Accepted values need to match minute intervals, so 300, 360, 420, etc.
+
 ## Channels
 
 The following table summarises the channels available for the ZSE09 -:
 
 | Channel | Channel Id | Category | Item Type |
 |---------|------------|----------|-----------|
 | sensor_binary | sensor_binary | Door | Switch | 
-| sensor_binary | sensor_binary | Door | Switch | 
 | alarm_motion | alarm_motion | Door | Switch | 
 | sensor_luminance | sensor_luminance |  | Number | 
 | Battery Level | battery-level | Battery | Number |
@@ -50,19 +116,6 @@ The following state translation is provided for this channel to the ```Switch```
 | ON | Triggered |
 | OFF | Untriggered |
 
-### sensor_binary
-
-Indicates if a sensor has triggered.
-
-The ```sensor_binary``` channel supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device.
-
-The following state translation is provided for this channel to the ```Switch``` item type -:
-
-| Value | Label     |
-|-------|-----------|
-| ON | Triggered |
-| OFF | Untriggered |
-
 ### alarm_motion
 
 Indicates if a motion alarm is triggered.

_addons_voices/picotts/readme.md

@@ -28,10 +28,6 @@ sudo apt-get install libttspico-utils
 In Arch Linux the pico2wave binaries are available in an Arch User repository (AUR) under
 https://aur.archlinux.org/packages/svox-pico-bin/
 
-## Configuration
-
-There is no need to configure anything for this service.
-
 ## Voices
 
 The following list are the only supported languages (as these are the languages supported by