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”?!?!
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.
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 ?