[Documentation] Markdown improvements t to z (#14371)

* Apply markdown fixes for bindings with letter _t_
* Apply markdown fixes for bindings with letter _u_
* Apply markdown fixes for bindings with letter _v_
* Apply markdown fixes for bindings with letter _w_
* Apply markdown fixes for bindings with letter _x_
* Apply markdown fixes for bindings with letter _y_
* Apply markdown fixes for bindings with letter _z_

Signed-off-by: Jerome Luckenbach <github@luckenba.ch>
This commit is contained in:
Jerome Luckenbach
2023-04-11 12:54:54 +02:00
committed by GitHub
parent 69a09ed825
commit ce3f673380
54 changed files with 1655 additions and 1778 deletions

View File

@@ -15,10 +15,9 @@ Parameter | Required | Description
`username` | yes | Username used to log in at [my.tado](https://my.tado.com)
`password` | yes | Password of the username
Example `tado.things`
```
```java
Bridge tado:home:demo [ username="mail@example.com", password="secret" ]
```
@@ -32,7 +31,7 @@ Name | Type | Description | Read/Write
## `zone` Thing
A *zone* is an area/room of your home.
A _zone_ is an area/room of your home.
You have defined them during installation.
One zone relates to one page in the tado° mobile- or webapp.
@@ -46,7 +45,7 @@ Zones can either be added through discovery or manually. Following up on the abo
Example `tado.things`
```
```java
Bridge tado:home:demo [ username="mail@example.com", password="secret" ] {
zone heating [id=1]
zone ac [id=2]
@@ -121,7 +120,7 @@ If parts of the setting are missing, then the currently active zone setting is u
If the termination condition is missing, the binding first checks if an override is active.
If that is the case, the existing termination condition is used.
An existing timer, for example, just keeps running.
An existing timer, for example, just keeps running.
In case the zone is currently in smart-schedule mode and thus doesn't have a termination condition, then the default termination condition is used, as configured in the tado° app (settings -> select zone -> manual control on tado° device).
## `mobiledevice` Thing
@@ -138,7 +137,7 @@ It is again easiest to refer to discovery in order to find the `id`.
Example `tado.things`:
```
```java
Bridge tado:home:demo [ username="mail@example.com", password="secret" ] {
mobiledevice phone [id=12345]
}
@@ -150,13 +149,13 @@ Name | Type | Description | Read/Write
-|-|-|-
`atHome` | Switch | ON if mobile device is in HOME mode, OFF if AWAY | R
Group `OR` can be used to define an item for *'is any device at home'*.
Group `OR` can be used to define an item for _'is any device at home'_.
# Full Example
## tado.things
```
```java
Bridge tado:home:demo [ username="mail@example.com", password="secret" ] {
zone heating [id=1]
zone ac [id=2]
@@ -168,7 +167,7 @@ Bridge tado:home:demo [ username="mail@example.com", password="secret" ] {
## tado.items
```
```java
Switch TADO_PRESENCE_home "Tado Presence: [MAP(presence.map):%s]" { channel="tado:home:demo:homePresence" }
Number:Temperature HEAT_inside_temperature "Inside Temperature" { channel="tado:zone:demo:heating:currentTemperature" }
Number HEAT_humidity "Humidity" { channel="tado:zone:demo:heating:humidity" }
@@ -203,7 +202,7 @@ Switch Phone_atHome "Phone location [MAP(presence.map)
## tado.sitemap
```
```perl
sitemap tado label="Tado"
{
Frame label="Status" {
@@ -255,7 +254,7 @@ sitemap tado label="Tado"
## presence.map
```
```text
ON=at home
OFF=away
NULL=lost