The unit of the item is used internally, in events and also for persistence. sending 5 Hz to a Number:Temperature channel) are discarded. 500 W will result in an item state of 0.5 kW). Values with units will be converted to that unit (i.e. 5 will result in the item state changing to 5 kW). kW that is used within openHAB that is independent from the unit that is used for displaying.Ī value that has no unit attached will be considered to be in that unit (i.e. if the thing sends 23 ☌), the item state will be 23.Īn item with dimension ( Number:Power) has a unit (e.g. Linking thing channels to such an item results in the unit being dropped (i.e. ![]() it invalidates your persisted data when you change the unit that is used for displaying. Unfortunately this still has issues, e.g. With openHAB 3.4 we already introduced a "default unit" that is used as the item's unit when no other units has been set. One of these issues is inconsistent handling of units when no state description for the item is defined. Since the introduction of UoM in openHAB 2.3 some limitations have been discovered. It has been refactored in openHAB 4 and needs some special attention when upgrading. Units of Measurement is used for handling values with units attached (like 23 ☌). Changes in Units of Measurement (UoM) Introduction Please read the following information carefully BEFORE starting the upgrade, since you might have to do some manual steps upfront. ![]() This is a monthly milestone build for the upcoming openHAB 4.0 release, which brings many fixes and improvements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |