updated generated content

Signed-off-by: Kai Kreuzer <kai@openhab.org>

_bindings/amazondashbutton/readme.md

@@ -68,7 +68,7 @@ Setting up your Dash button is as simple as following the instructions provided
 
 ## Block Internet access for the Dash Button
 
-Completely deny internet access for the Amazaon Dash Button in your router. You need to find out the Dash button's IP address first of all. This is not explained as this job depends on your environment.
+Completely deny internet access for the Amazon Dash Button in your router. You need to find out the Dash button's IP address first of all. This is not explained as this job depends on your environment.
 
 
 ## Supported Things
@@ -101,7 +101,7 @@ __ Caution:__  You have to be aware that other Amazon devices might pop up in yo
 ```
 rule "Dash button pressed"
     when
-        Channel "amazondashbutton:dashbutton:ac-63-be-xx-xx-xx:press" triggered
+        Channel "amazondashbutton:dashbutton:ac63bexxxxxx:press" triggered
     then
         println("The Dash button has been pressed")
 end

_bindings/mqtt1/readme.md

@@ -104,7 +104,7 @@ Number temperature "temp [%.1f]" {mqtt="<[publicweatherservice:london-city/tempe
 Number waterConsumption "consum [%d]" {mqtt="<[mybroker:myHome/watermeter:state:XSLT(parse_water_message.xslt)]"} 
 Switch doorbell "bell [%s]" {mqtt="<[mybroker:myHome/doorbell:command:ON]"}
 Number mfase1 "mfase1 [%.3f]" {mqtt="<[flukso:sensor/9cf3d75543fa82a4662fe70df5bf4fde/gauge:state:REGEX(.*,(.*),.*)]"}
-Number humidity "humidity [%.1f%%] {mqtt="<[broker:weatherstation/readings:state:JS(convertPercent.js):humidity=.*]"}
+Number humidity "humidity [%.1f%%]" {mqtt="<[broker:weatherstation/readings:state:JS(convertPercent.js):humidity=.*]"}
 ```
 
 ## Item Configuration for Outbound Messages

_bindings/onebusaway/readme.md

@@ -0,0 +1,96 @@
+---
+id: onebusaway
+label: OneBusAway
+title: OneBusAway - Bindings
+type: binding
+description: "[OneBusAway](https://onebusaway.org/) is an open source, real-time, transit-information service.  This binding allows you to get events based on transit arrival and departures, so you can create rules to do something based on that data."
+since: 2x
+install: auto
+---
+
+<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
+
+{% include base.html %}
+
+# OneBusAway Binding
+
+[OneBusAway](https://onebusaway.org/) is an open source, real-time, transit-information service.  This binding allows you to get events based on transit arrival and departures, so you can create rules to do something based on that data.
+
+## Preparation
+
+You'll need to obtain an API key from the transit provider you want to load data from.  Different providers of the service have different policies, so you'll have to figure this part out for each [deployment](https://github.com/OneBusAway/onebusaway/wiki/OneBusAway-Deployments). 
+
+## Supported Things
+
+This binding supports route arrival and departure times for all stops provided from a OneBusAway deployment.
+
+## Binding Configuration
+
+The following configuration options are available for the API binding:
+
+| Parameter | Name | Description | Required |
+|-----------|------|-------------|----------|
+| `apiKey` | API Key | The API key given to you by a transit provider for their deployment. | yes |
+| `apiServer` | API Server | The domain name of the deployment to talk to, e.g. `api.pugetsound.onebusaway.org`. | yes |
+
+The following configuration options are available for the Stop binding (which requires an API binding):
+
+| Parameter | Name | Description | Required |
+|-----------|------|-------------|----------|
+| `stopId` | Stop ID | The OneBusAway ID of the stop to obtain data for, e.g. `1_26860`. | yes |
+| `interval` | Update Interval | The number of seconds between updates. | no |
+
+## Thing Configuration
+
+The following configuration options are available for a Route (which requires a Stop binding):
+
+| Parameter | Name | Description | Required |
+|-----------|------|-------------|----------|
+| `routeId` | Route ID | The OneBusAway ID of the route to obtain data for, e.g. `1_102574`. | yes |
+
+## Channels
+
+The Route Thing supports the following state channels:
+
+| Channel Type ID | Channel Kind | Item Type | Description |
+|-----------------|--------------|-----------|-------------|
+| arrival | state | DateTime | The arrival time of a Route at a Stop. |
+| departure | state | DateTime | The departure time of a Route at a Stop. |
+| update | state | DateTime | The last time this data was updated (per the data provider, not the last time OpenHAB updated the data). |
+| arrivalDeparture | trigger | DateTime | Triggered when a Route arrives or departs a Stop. |
+
+### Channel Configurations
+
+The `arrival`, `departure`, and `arrivalDeparture` channels can be configured with an `offset` specifying the number of seconds to move an event back in time.
+
+## Full Example
+
+Here's an example of a configuration for a bus stop in Seattle, WA, USA that has three routes configured.
+
+`demo.things`:
+
+```
+Bridge onebusaway:api:pugentsound [apiKey="your-api-key", apiServer="api.pugetsound.onebusaway.org"] {
+  Bridge onebusaway:stop:1_26860 [stopId="1_26860"] {
+    Thing onebusaway:route:1_100193 [routeId="1_100193"]
+    Thing onebusaway:route:1_102574 [routeId="1_102574"]
+    Thing onebusaway:route:1_100252 [routeId="1_100252"]
+  }
+}
+```
+
+`demo.items`:
+
+```
+// Route 1_100193 (#32)
+DateTime Fremont_32_Arrival "32 - University District" { channel="onebusaway:route:1_100193:arrival" }
+DateTime Fremont_32_Departure "32 - University District" { channel="onebusaway:route:1_100193:departure" }
+
+// Route 1_102574 (#40)
+DateTime Fremont_40_Arrival "40 - Ballard" { channel="onebusaway:route:1_102574:arrival" }
+DateTime Fremont_40_Departure "40 - Ballard" { channel="onebusaway:route:1_102574:departure" }
+
+// Route 1_100252 (#62)
+DateTime Fremont_62_Arrival "62 - Sand Point East Green Lake" { channel="onebusaway:route:1_100252:arrival" }
+DateTime Fremont_62_Departure "62 - Sand Point East Green Lake" { channel="onebusaway:route:1_100252:departure" }
+```

_bindings/zigbee/readme.md

@@ -0,0 +1,66 @@
+---
+id: zigbee
+label: ZigBee
+title: ZigBee - Bindings
+type: binding
+description: "The ZigBee binding supports an interface to a wireless ZigBee home automation network."
+since: 2x
+install: auto
+---
+
+<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
+
+{% include base.html %}
+
+---
+layout: documentation
+---
+
+{% include base.html %}
+
+# ZigBee Binding
+The ZigBee binding supports an interface to a wireless ZigBee home automation network. 
+
+
+## Supported Things
+
+### ZigBee TI2531 Coordinator
+
+Before the binding can be used, a coordinator must be added. This needs to be done manually and the serial port must be set.
+
+
+## Discovery
+
+Once the binding is authorized, and an adapter is added, it automatically reads all devices that are set up on the ZigBee controller and puts them in the Inbox.
+
+## Binding Configuration
+
+
+
+## Thing Configuration
+
+The binding will attempt to automatically detect new devices, and will read their supported clusters upon startup. A set of channels will then be created depending on what clusters and endpoints a device supports.
+
+The following devices have been tested with the binding -:
+
+
+
+
+## Channels
+
+
+## TI2531 - Firmware
+
+The TI2531 USB dongle must be flashed with the correct firmware in order to work with this binding.
+The file can be downloaded from TI website archives (http://www.ti.com/tool/z-stack-archive) as part
+of the `Z-STACK-HOME v.1.2.2a` package.
+The file name is `CC2531ZNP-Pro-Secure_Standard.hex` and its sha256 is `3cc5dc571ef0f49e3f42c6c2ca076d6f8fef33a945c71e6f951b839ba0599d3c`.
+
+### Flashing on Linux
+
+It's possible to flash the dongle using Linux, using `cc-tool` (https://github.com/dashesy/cc-tool.git).
+The software has been tested and confirmed working on Ubuntu 16.10 and 17.04.
+The required dependencies can be installed with `sudo apt install build-essential libusb-1.0-0-dev libboost-all-dev`,
+and the binary compiled with `./configure && make`. Do not forget to install the `udev` rules, as described at https://github.com/dashesy/cc-tool/blob/master/README , or the software might not be able to access the USB programmer.
+
+The firmware can be flashed with `./cc-tool -e -w CC2531ZNP-Pro-Secure_Standard.hex -v r`. Change the path to the firmware accordingly.

_repos/openhab

@@ -1 +1 @@
-Subproject commit 817ca775fa840efff386787cc763c3fddc07397e
+Subproject commit e11b8929c359e1dfbf20f8832503a3062e0a6b02

_repos/openhab-bundles

@@ -1 +1 @@
-Subproject commit eba0094465c37d42089c26ada127e734a4ba0e56
+Subproject commit f85adc1acf3d9c7861bbbf36a79837a31a9d3cb1

_repos/openhab-distro

@@ -1 +1 @@
-Subproject commit 313701d28b974073051d93ffd0b013007ef75f48
+Subproject commit b9f699c1b1e8839269bd7db560c7d30f34138230

_repos/openhab2-addons

@@ -1 +1 @@
-Subproject commit 063f1cf7907353700a46bb52b5ada93baee31e2c
+Subproject commit 875b61eafedba22d44840ccb836dd15f62033c9d

_repos/smarthome

@@ -1 +1 @@
-Subproject commit f4f70010248494abccd8af7fec6ca2332041569b
+Subproject commit 1b8405b22f26cb1546d2fea143fd254e11d65edc

update.sh

@@ -18,7 +18,7 @@ git pull
 cd ../openhab-bundles
 git checkout master
 git pull
-git submodule update --recursive --remote
+git submodule update --recursive --remote --init
 
 cd ../openhab-distro
 git checkout master