OS: Debian 1.7, official OH3.0.0 Docker image deployed in K3S
Java Runtime Environment: Java 11
openHAB version: OH3.0.0
Issue of the topic:
I’ve tested to connect to my production environment running OH2.5 from my OH3 testbed using the Remote openHAB binding (really cool and useful binding ).
I then installed the exact same binding in my production environment as in OH3 and created the exact same item for a temperature sensor on my car. In the items list both behaves the same and display both measurement unit and decimals.
I get the same behaviour when testing other temperature items from other bindings in my production environment so it seems to be isolated to items that are imported via the remote openHAB binding.
What cold cause that behaviour? Is there any w.o.?
Click on add metadata and configure the Item state formatting (or something like that) the same as it’s defined on OH 2. You can have even more control over how that card looks by defining a custom default card widget and you can have full control over it. someone’s the default isn’t that smart.
Was your items created with the new UI ?
The remote openHAB binding is not retrieving the “pattern” from the remote item. So be sure to define a “pattern” including the unit for your item in your main server.
This should be mentioned in the binding documentation.
This is not easy to enhance but you can open an enhancement request for this feature in Git.
Yes, that is what this thread is about since I test the remote OH binding to integrate from my OH2.5.x production towards my OH3 testbed, the issue is that the OH remote binding does not handle the original remote item patterns at all.
In my production environment this items is defined as:
Number Oregon_Outdoor_Humidity_Front "Oregon Front Humidity [%d %%]" <humidity> {channel="tellstick:sensor:1:15_F824_oregon:humidity"}
and their it displays the humidity correctly in a sitemap:
But when I use the same item via remote OH binding and set the same pattern in metadata, since it is not handled by the binding, the value is displayed * 100.
But that is not a Quantity type Item. It has no units, though you can specify a bit of text to be shown in display with it, like %.
You can’t map that to a Number:Dimensionless type Item because its value, its raw state, has no units.
Or rather you can, because Dimensionless is the one Quantity type that accepts a number with no units, but you won’t get the value you expect.
Yes, of course, the same item type has to be used. I will not change that because I can’t.
What I would like to provide by default is the same pattern formatter and this will work if you use the same item type.