Weird behavior of item prediction with KNX2 binding

Setup, Configuration and Use Scripts & Rules
1

I am using openHAB 2.4 (migrated from 2.1 a few days ago). Now i have some weird behavior regarding item prediction with KNX2 binding.

e.g: a simple switch with KNX2 binding:

item

Switch Licht_EG_Vorraum					"Licht Eingang"					<light>				(EG_Diele, Beleuchtung, Haus_Aus)			[ "Switchable" ]	{channel="knx:device:bridge:Actuator_2:Licht_EG_Vorraum"}

KNX.things

Thing device Actuator_2 [
        address="1.0.4",
        fetch=false,
        pingInterval=1800
    ] {
		Type switch        : Licht_EG_Vorraum   		"Licht Eingang"	 					[ ga="1/0/110+<1/3/110" ]	
    }

sitemap

Switch item=Licht_EG_Vorraum			label="Decke"

enents

2019-01-06 09:08:08.809 [ome.event.ItemCommandEvent] - Item 'Licht_EG_Vorraum' received command ON
2019-01-06 09:08:08.809 [nt.ItemStatePredictedEvent] - Licht_EG_Vorraum predicted to become OFF
2019-01-06 09:08:08.842 [vent.ItemStateChangedEvent] - Licht_EG_Vorraum changed from OFF to ON

2019-01-06 09:08:10.478 [ome.event.ItemCommandEvent] - Item 'Licht_EG_Vorraum' received command OFF
2019-01-06 09:08:10.479 [nt.ItemStatePredictedEvent] - Licht_EG_Vorraum predicted to become ON
2019-01-06 09:08:10.510 [vent.ItemStateChangedEvent] - Licht_EG_Vorraum changed from ON to OFF

The prediction seems on the wrongs side always?!?!?
Is there a possibility to change the configutation in a way to act like openHAB 2.1?

Maybe all items with KNX binding should be set to autoupdate=“false”?!?!

2

Could you solve your problem? I have the same behaviour!

3

Yes, autoupdate=“false” did it

4

I am a great believer in disabling autoupdate where you get timely status updates from a real device. Saves clutter in logs, apart from wasted processing.

but -
This does look like a error in autoupdate process. It’s only guessing, but command=ON to state=ON seems like an easy guess.
As the binding itself can make “suggestions” about autoupdate predictions in OH 2.4, and autoupdate seems to work okay with switches in other situations - perhaps a KNX binding bug or misconfiguration.

Same issue reported here

I am not a KNX person but I wonder if @Udo_Hartmann would have a more expert opinion here ?

5

Well, I must confess, I didn’t figure aout the prediction thing yet.
As all my knx items are configured to autoupdate="false" anyway…

6

any update ? have similar problem

7

I doubt there would be any change unless someone produces a good example and raises a github issue for it.