Last Updated on 2017-06-28.
[:en]
Scenario
openHAB is basically working, but does not always update items when they change (e.g. when a window contact closes or opens).
However, testing via ETS works.
Reason
openHAB, especially version 2.x, offers a new option for the KNX interface configuration, “ignorelocalevents”.
At first sight, it looks like a good idea to set it to “true”, but what happens is that every message from sender “0.0.0” is ignored, because openHAB sees itself as 0.0.0 (local) by default.
If you work with KNX devices or interfaces which do not necessarily own a physical sender address (like any Home Automation Server from Gira, Loxone, … or with eibd / BCU SDK), they might also use the KNX sender address 0.0.0 by default, which leads to packets (telegrams) being ignored by openHAB.
Solution
IMHO, the best way is to give openHAB a “physical”, unallocated address like 1.1.240.
If you want to stay with PA 0.0.0, set “ignorelocalevents” to false. Note, this seems not to be recommended by the OH2 developers, as it should provide only backwards compatibility.
So a working openHAB2 KNX config could look like:
#(example uses eibd on Ubuntu as KNX interface) ip=10.1.0.52 #type=ROUTER type=TUNNEL timeout=2000 ignorelocalevents=true port=3671 autoReconnectPeriod=30 busaddr=1.1.240
[:]