[KNX] DPT 5.001 on KNX2 Binding delivers decimal instead of percentage values

When using DPT 5.001 to read a value from my heating actuator, the binding delivers a decimal (e.g. 0.6) instead of a percentage (e.g. 60%). These values are sent correctly by the actuator to the KNX bus and have been processed correctly on the OH2 side with the KNX1 binding as well. Can somebody please have a look at this ?

Thanks a lot

Running OH2 snapshot 2.4.0~20181018164807-1 (Build #1399) on Openhabian on a RPi3b+, using a Enertex Router to Access the bus.

things

Thing device HA1MDTREG "HA1 MDT Heizungsaktor Heizkeller" @ "KNX" [ address="1.1.200", fetch=false, pingInterval=600, readInterval=0]
{
Type    number  :       Channel08         "Heizung Wohnzimmer Stellwert"      [ ga="5.001:<13/1/0" ]
}

items

Number HeizungWoZiStellwert	Stellwert [%.1f %%]" { channel="knx:device:KNXRouter:HA1MDTREG:Channel08" }

[marcoavnet]

Hello, allow to give my two cents to this topic. I recently upgraded to OH 2.5.3 and for me the new KNX binding. Same observations as in this thread and I have the “Workaround” with the dimmer item.

In my opinion a number item is the correct one for percentage values. Having to use a dimmer item is a workaround. A humidity value has nothing to do with dimmer. If DPT 5.001 is used the conversion should be done automatically.

[ustone]

Can somebody explain why this is closed? IMO KNX defines DPT 5.001 like this:

8-bit unsigned value | 1 Byte | DPT 5.001 | DPT 5.001 | 0…100

Values are 0…100 as you see. That means, if the ga section in things is like ga=“5.001:<13.13.13”, the values has to be converted in percent value or ga=“5.001:<13.13.13” is invalid and must ga=“<13.13.13”. Why else the knx binding accept an KNX Datatype?

Additionally i wonder that knx 1 had the conversion by default and this ugly workaround switching to dimmer is accepted for KNX 2.

Have i misinterpreted the design of the knx 2 binding?