OpenHAB
/
openhab-docs
mirror of https://github.com/openhab/openhab-docs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated external content (Jenkins build 2638)

pull/2522/head
openHAB Build Server 2025-05-30 06:00:13 +00:00
parent 7c045b4c59
commit bb34e3e384
2 changed files with 17 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
_addons_bindings/tado/readme.md
View File

@ -29,33 +29,29 @@ You can then monitor and control all zone types (Heating, AC, Hot Water) as well
The `home` thing serves as bridge to the tado° cloud services. The `home` thing serves as bridge to the tado° cloud services.
The binding will automatically discover this thing and place it in the Inbox. The binding will automatically discover this thing and place it in the Inbox.
It must be authenticated before it will actually go online. It must be authenticated before it will actually go online.
There are two ways to authenticate it as follows: Authenticatation is done online via the OAuth Device Code Grant Flow (RFC-8628) authentication process via the link provided at `http://[openhab-ip-address]:8080/tado`.
1. Online via the OAuth Device Code Grant Flow (RFC-8628) authentication process through the link provided at `http://[openhab-ip-address]:8080/tado`. | Parameter | Optional | Description |
1. Enter `username` and `password` credentials in the thing configuration parameters as shown in the table below. |---------------|----------|-------------------------------------------------------------------------------|
| `rfcWithUser` | yes | Determines if the user name is included in the oAuth RFC-8628 authentication. |
| `username` | yes | Selects the tado° account to be used if there is more than one account. |
| `homeId` | yes | Selects the Home Id to use in case of more than one home per account. |
Note: after March 15th, 2025 online authentication is the tado° preferred (or even only) method. The `rfcWithUser` and `username` settings are only needed if you have more than one tado° account.
In other words the `username` and `password` method has probably ceased to work after that date. The `rfcWithUser` setting makes the binding use a different authentication token for each respective account `username`.
| Parameter | Optional | Description | The `homeId` is only needed if you have more than one home under a given tado° account.
|---------------|----------|------------------------------------------------------------------------------------|
| `useRfc8628` | yes | Determines if the binding shall use oAuth RFC-8628 authentication |
| `rfcWithUser` | yes | Determines if the user name shall be included in the oAuth RFC-8628 authentication |
| `username` | yes | Username used to log in at [my.tado](https://my.tado.com) |
| `password` | yes | Password of the username |
| `homeId` | yes | Selects the Home Id to use (only needed if the account has multiple homes) |
The `rfcWithUser` setting is only needed if you have multiple tado° accounts.
It forces the binding to use different authentication tokens for each respective account `username`.
The `homeId` is only needed if you have multiple homes under a single tado° account.
It forces the binding to read and write the data for the respective Home Id. It forces the binding to read and write the data for the respective Home Id.
If you do not have multiple homes, the binding always uses the first and only Home Id. If you do not have multiple homes, the binding always uses the first and (therefore) only Home Id.
Example `tado.things` Example `tado.things`
```java ```java
Bridge tado:home:demo [ username="mail@example.com", password="secret" ] // normal example with one tado° account containing one home
Bridge tado:home:demo
..
// special case if you have more than one tado° account, or more than one home in an account
Bridge tado:home:demo [ rfcWithUser=true, username="mail@example.com", homeId=1234 ]
``` ```
Once the `home` thing is online, the binding will discover all its respective zones and mobile devices, and place them in the Inbox. Once the `home` thing is online, the binding will discover all its respective zones and mobile devices, and place them in the Inbox.

16
_thing_types/org.openhab.binding.tado/src/main/resources/OH-INF/thing/thing-types.xml
View File

@ -20,11 +20,6 @@
</properties> </properties>
<config-description> <config-description>
<parameter name="useRfc8628" type="boolean" required="false">
<label>Use oAuth RFC-8628</label>
<description>Determines if the binding shall use oAuth RFC-8628 authentication</description>
</parameter>
<parameter name="rfcWithUser" type="boolean" required="false"> <parameter name="rfcWithUser" type="boolean" required="false">
<label>RFC-8628 with User</label> <label>RFC-8628 with User</label>
<description>Determines if the user name is included in the oAuth RFC-8628 authentication</description> <description>Determines if the user name is included in the oAuth RFC-8628 authentication</description>
@ -33,20 +28,13 @@
<parameter name="username" type="text" required="false"> <parameter name="username" type="text" required="false">
<label>User Name</label> <label>User Name</label>
<description>User name of tado login used for API access</description> <description>Selects the tado° account to be used if there is more than one account.</description>
<advanced>true</advanced>
</parameter>
<parameter name="password" type="text" required="false">
<label>Password</label>
<description>Password of tado login used for API access</description>
<context>password</context>
<advanced>true</advanced> <advanced>true</advanced>
</parameter> </parameter>
<parameter name="homeId" type="integer" required="false"> <parameter name="homeId" type="integer" required="false">
<label>Home Id</label> <label>Home Id</label>
<description>Selects the Home Id to be used (only needed if there are multiple homes)</description> <description>Selects the Home Id to be used if there is more than one home per account.</description>
<advanced>true</advanced> <advanced>true</advanced>
</parameter> </parameter>
</config-description> </config-description>