[remoteopenhab] Try to clarify that remote state channels will not be available (#9349)

Signed-off-by: Laurent Garnier <lg.hc@free.fr>
pull/9355/head
lolodomo 2020-12-13 08:58:57 +01:00 committed by GitHub
parent 8f53e320dc
commit fcad4826a6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 3 deletions

View File

@ -77,7 +77,10 @@ Only basic groups (with no state) from the remote server are ignored.
The channel ID of the created channel corresponds to the name of the item on the remote server.
For example, if your remote item is named `MyDate`, the channel UID of the channel created by the binding will be `remoteopenhab:server:xxx:MyDate`.
On the `thing` thing, if the `buildTriggerChannels` parameter is set to true, a channel is created automatically for each trigger channel defined in the remote thing.
On the `thing` thing, you will not find all channels from your remote thing.
Only trigger channels from your remote thing will be created.
**All state channels from your remote thing will be ignored** (use the `server` thing to link a local item to a remote (item).
if the `buildTriggerChannels` parameter is set to true, a channel is created automatically for each trigger channel defined in the remote thing.
For example, if your remote thing provides a trigger channel with this UID `astro:sun:local:night#event`, the channel UID of the channel created by the binding will be `remoteopenhab:thing:xxx:astro_sun_local_night_event`.
## Limitations

View File

@ -6,7 +6,7 @@
<bridge-type id="server">
<label>Remote openHAB Server</label>
<description>A remote openHAB server.</description>
<description>A remote openHAB server. You will find one channel for each item defined in the remote server.</description>
<representation-property>host</representation-property>
@ -77,7 +77,8 @@
</supported-bridge-type-refs>
<label>Remote Thing</label>
<description>A thing from the remote openHAB server.</description>
<description>A thing from the remote openHAB server. You will find one channel for each trigger channel from the
remote thing (state channels from the remote thing will be ignored).</description>
<representation-property>thingUID</representation-property>