[remoteopenhab] Considering the remote item pattern formatter #9645
Labels
enhancement
An enhancement or new feature for an existing add-on
Comments
lolodomo
added
the
enhancement
lolodomo
added a commit
to lolodomo/openhab-addons
that referenced
this issue
Jan 2, 2021
Fux openhab#9645 Signed-off-by: Laurent Garnier <[email protected]>
cpmeister
pushed a commit
that referenced
this issue
Jan 4, 2021
* [remoteopenhab] Consider the remote item pattern formatter Fux #9645 * Review comment: use computeIfAbsent Signed-off-by: Laurent Garnier <[email protected]>
thinkingstone
pushed a commit
to thinkingstone/openhab-addons
that referenced
this issue
Nov 7, 2021
) * [remoteopenhab] Consider the remote item pattern formatter Fux openhab#9645 * Review comment: use computeIfAbsent Signed-off-by: Laurent Garnier <[email protected]>
marcfischerboschio
pushed a commit
to bosch-io/openhab-addons
that referenced
this issue
May 5, 2022
) * [remoteopenhab] Consider the remote item pattern formatter Fux openhab#9645 * Review comment: use computeIfAbsent Signed-off-by: Laurent Garnier <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the remote openHAB binding considers whether the remote item is read-only or not; it also considers the state options from the remote item. But it does not yet consider the remote item pattern formatter as pattern for the local channel (and so linked local item).
One of the consequence is that for example if your remote item is set to display a unit, your local item will not have this unit displayed by default. You will have to setup it additionally in the main server.
The enhancement will consist in applying the same pattern formatter as the one defined for the remote item.
Technically, this will imply more or less to create one channel type for each remote item, rather than using few generic channel types).
I will try to implement this enhancement.
The text was updated successfully, but these errors were encountered: