I have an KNX router running on a Raspberry PI3 B+. I can communicate with ETS software and other smart home apps like the home app withe home bridge knxd or the ayControl are working without any problems.
I used as binding in OH the following configuration in knx.things:
After setting the locaSourceAddr to 0.0.0, it is getting more worse. Before OH was receiving the datagrams, which were triggered a device. When I was turning on/off the light with my ight switch at the wall, OH was
seeing them and on my GUI, the lamp switches from ON to OFF and the other way round.
Now OH does not receive any more this triggered datagrams
I have still the problem, that I can only receive KNX telegrams from the bus, but I can not write anything to the bus. I have now limited the number of clients on the KNXD to 1, so that only one
is in use. Here is the configuration file of the knxd:
Why should the config of the KNXD be problematic?
ETS5 is working without any problems. Other tools like
knx for Homebridge or ayControl are working. Only
the OH2 KNX Binding make problems
in addition: a) other endpoints most likely are using unicast & b) in multicasting, IAs and other parameters need properly configured options to work… something that I don’t see in your knxd
I just was doing test and using Wireshark to capture the traffic on the network.
Using ETS or other apps then OH produce traffic on the lan interface. When I
try to switch on/off the light, I can see no traffic at all on the network.
So it can not be the KNX configuration why OH is not working.