[knx] Unexpected behavior using DTP 5.001
See original GitHub issueTested on a 2.4.0-SNAPSHOT Build #1401 on Windows, with only KNX2 binding installed.
Expected Behavior
- I would expect that DTP 5.001 can also be configured as a number thing.
- The loosing of the KNX packets when DTP 5.001 configured as number should minimum raise a warning?!
Current Behavior
DTP 5.001 correctly configured to get percent value: KNX Thing in ./conf/things/*.thing: it normally has to be Type dimmer
Type dimmer :OG_mitte_Status_Stellwert_0_2_42 "OG mitte Status Stellwert" [ position="5.001:<0/2/42", autoupdate="true" ] // 1 byte K L - U - Prozent (0..100%)
KNX Item in ./conf/items/*.item: it normally has to be Dimmer Item
Dimmer OG_mitte_Status_Stellwert_0_2_42 "OG mitte Status Stellwert [%d %%]" (OG, gHeizaktoren, gMitte, gSQLeveryDayChange) { channel="knx:device:bridge:knx_heataktors:OG_mitte_Status_Stellwert_0_2_42" }
Log output: Use dimmer thing as Dimmer Item:
2018-10-27 08:44:11.433 [vent.ItemStateChangedEvent] - OG_mitte_Status_Stellwert_0_2_42 changed from 100 to 8
Use dimmer thing as Number Item:
08:49:04.398 [INFO ] [smarthome.event.ItemStateChangedEvent] - OG_mitte_Status_Stellwert_0_2_42 changed from 0.08000000 to 1.00000000
When I switch my thing to Type number or Item AND Thing to number, I get no update from the KNX bus anymore. It does not matter if i have defined my thing with or without DTP definition
position="5.001:<0/2/42".
It would be desirable if we could define DTP 5.001 alternatively as a number in the Things. It seems to me at least not logical because this behavior leads to confusion.
The loosing of the KNX packets is not correct. In addition, the KNX binding does not even raise a warning for this case.
Originally we discussed here: https://github.com/openhab/openhab2-addons/issues/4146
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:11 (3 by maintainers)

Top Related StackOverflow Question
@bjoernbrings, knx2 is relatively new, we have to improve it bit by bit. @zaphood1967, currently I can not come up with a solution or reproduce the behavior. But I will keep your observation in mind.
closed due to inactivity