public/openhab-addons
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[remoteopenhab] Fix Remote openHAB Readme typos and introduce non-breaking spaces in 'openHAB v' for readability (#9652)

Browse Source 
Signed-off-by: Stefan Gänsler <openhab-git_19@green-sparklet.de>
This commit is contained in:
Stefan 2021-01-06 21:44:18 +01:00 committed by GitHub
parent 813ac27c0e
commit 911cd01e17
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
bundles/org.openhab.binding.remoteopenhab/README.md
View File

@ -9,11 +9,11 @@ Through this mapping, in your rules (local server), you can take actions based u
One use of this binding is to distribute your home automation system on multiple openHAB servers. One use of this binding is to distribute your home automation system on multiple openHAB servers.
Another use is for users to interact with older versions of openHAB that may support old openHAB v1 bindings that were not migrated to openHAB v2 or openHAB v3. Another use is for users to interact with older versions of openHAB that may support old openHAB v1 bindings that were not migrated to openHAB v2 or openHAB v3.
They can keep an openHAB v2 server to run their old openHAB v1 bindings and setup a new openHAB v3 server for everything else. They can keep an openHAB v2 server to run their old openHAB v1 bindings and setup a new openHAB v3 server for everything else.
The Remote openHAB binding installed on the openHAB v3 server will then allow to use the openHAB v1 bindings through communication with the openHAB v2 server. The Remote openHAB binding installed on the openHAB v3 server will then allow to use the openHAB v1 bindings through communication with the openHAB v2 server.
A third usage is for users that would like to keep unchanged an existing openHAB v2 server but would like to use the new UI from openHAB v3; they can simply setup a new openHAB v3 server with the Remote openHAB binding linked to their openHAB v2 server. A third usage is for users that would like to keep unchanged an existing openHAB v2 server but would like to use the new UI from openHAB v3; they can simply setup a new openHAB v3 server with the Remote openHAB binding linked to their openHAB v2 server.
## Supported Things ## Supported Things
@ -30,7 +30,7 @@ Once a bridge thing representing a remote openHAB server is created, all things
## Binding Configuration ## Binding Configuration
The binding has no configuration options, all configuration is done at Thing level. The binding has no configuration options, all configuration is done at thing level.
## Thing Configuration ## Thing Configuration
@ -54,7 +54,7 @@ The `thing` thing has the following configuration parameters:
| thingUID | yes | The thing UID in the remote openHAB server. | | thingUID | yes | The thing UID in the remote openHAB server. |
| buildTriggerChannels | no | If set to true, a trigger channel will be automatically created and linked to each trigger channel from the remote thing. Default is true. | | buildTriggerChannels | no | If set to true, a trigger channel will be automatically created and linked to each trigger channel from the remote thing. Default is true. |
Please note that if your remote server is an openHAB v3 server, you will need to define a valid token on your bridge thing to have your things correctly initialized. Please note that if your remote server is an openHAB v3 server, you will need to define a valid token on your bridge thing to have your things correctly initialized.
Setting the `buildTriggerChannels` parameter to false is for the main following advanced usages: Setting the `buildTriggerChannels` parameter to false is for the main following advanced usages:
@ -85,7 +85,7 @@ For example, if your remote thing provides a trigger channel with this UID `astr
## Limitations ## Limitations
* The binding will not try to communicate with an openHAB v1 server. * The binding will not try to communicate with an openHAB v1 server.
## Example ## Example