OH3 KNX Binding converts 20.102 enum into float

Dear all,

I am experiencing a wrong conversion issue with KNX DPT 20.102 objects:


Thing device Stetigregler_GaesteWC "Stegigregler EG Gäste WC" (knx:ip:tunnel) [
] {
    Type number        : Temperatur         "Temperatur EG Gäste WC"           [ ga="<1/2/5" ]
    Type number        : Betriebsmodus      "Betriebsmodus EG Gäste WC"        [ ga="20.102:<1/4/24" ]



Number Betriebsmodus_EG_GaesteWC “Betriebsmodus Gäste WC [MAP(rtr.map):%s]” (EG_GaesteWC, gBetriebsmodus) {channel=“knx:device:tunnel:Stetigregler_GaesteWC:Betriebsmodus”}

Expected result after update from KNX bus should be an integer, but its sometimes a float:

/var/log/openhab/events.log:2021-01-11 08:15:15.622 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Betriebsmodus_EG_GaesteWC’ changed from 2 to 1.0

/var/log/openhab/events.log:2021-01-11 08:16:24.121 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Betriebsmodus_EG_GaesteWC’ changed from 1.0 to 2.0

Any ideas how to troubleshoot this further? The result should always be an integer value (DPT HVAC enum type).



I have the same problem with DPT 20.102. I tryed DPT 5.004 that is a byte reading as 20.102 (0…255), here I get NULL, that will say nothing.
Here is how my channels lokk:

  • id: soverom_test1
    channelTypeUID: knx:number
    label: Soverom Test 1
    description: “”
    ga: 20.102:1/4/7
  • id: soverom_test2
    channelTypeUID: knx:number
    label: Soverom Test 2
    description: “”
    ga: 5.004:1/4/7

For me this works:

Type number : bBadModus “Bad Betriebsmodus” [ga=“5.010:5/3/14+<5/3/15”]


Works for me too :slight_smile:

Hi Rune, Markus,

many thanks for jumping in here. I changed my config to

Type number : Betriebsmodus “Betriebsmodus EG Gäste WC” [ ga=“5.010:<1/4/24” ]

Unfortunately without success:

knxtool groupwrite ip: 1/4/24 1

lead to

events.log:2021-01-11 19:13:29.467 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Betriebsmodus_EG_GaesteWC’ changed from 2.0 to 1.0

Running OH3 distro with 3.0.0 KNX Binding the problem still persists.

Any hint to troubleshoot is highly appreciated. Thanks,