KNX Binding 2.3

Add-ons Bindings
1

Hey,

Just finished migration toward Openhab 2.4 with KNX binding 2.3.
All configuration has been done through the GUI instead of text files (6 hours of clicking and typing, but everything is moved now). :wink:
At first sight, everything is working as before. So far, so good.

For my IP-router (knx convertor), I’ve left the local IP empty, and the local KNX GA also empty. When I fill in 1.1.1 (what i thought my GA adress was), all other KNX things stay offline. When I leave it empty (0.0.0?), the devices come online.

When I added the things, I selected the option ‘Read out the device parameters and address/communication object tables’. Thought it would read out all GA’s and so. But at first sight, seems not to work.

Now, I think that this option (read out) gives me some errors:

2018-06-14 11:22:48.465 [WARN ] [calimero.mgmt.MC 192.168.222.89:3671] - problem reading property (response 43 d6 00 4e 00 01)
tuwien.auto.calimero.KNXRemoteException: property access OI 0 PID 78 failed/forbidden
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.extractPropertyElements(ManagementClientImpl.java:986) ~[?:?]
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.lambda$readProperty$0(ManagementClientImpl.java:570) ~[?:?]
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.waitForResponses(ManagementClientImpl.java:905) ~[?:?]
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.readProperty(ManagementClientImpl.java:568) ~[?:?]
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.readProperty(ManagementClientImpl.java:535) ~[?:?]
    at org.openhab.binding.knx.internal.client.DeviceInfoClientImpl.lambda$2(DeviceInfoClientImpl.java:107) ~[?:?]
    at org.openhab.binding.knx.internal.client.DeviceInfoClientImpl.readFromManagementClient(DeviceInfoClientImpl.java:56) ~[?:?]
    at org.openhab.binding.knx.internal.client.DeviceInfoClientImpl.readDeviceProperties(DeviceInfoClientImpl.java:105) ~[?:?]
    at org.openhab.binding.knx.internal.client.DeviceInspector.readDeviceProperties(DeviceInspector.java:108) ~[?:?]
    at org.openhab.binding.knx.internal.client.DeviceInspector.readDeviceInfo(DeviceInspector.java:88) ~[?:?]
    at org.openhab.binding.knx.handler.AbstractKNXThingHandler.describeDevice(AbstractKNXThingHandler.java:89) ~[?:?]
    at org.openhab.binding.knx.handler.AbstractKNXThingHandler.lambda$0(AbstractKNXThingHandler.java:153) ~[?:?]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
    at java.lang.Thread.run(Thread.java:748) [?:?]
2018-06-14 11:22:49.288 [WARN ] [calimero.mgmt.MC 192.168.222.89:3671] - problem reading property (response 43 d6 00 4e 00 01)
tuwien.auto.calimero.KNXRemoteException: property access OI 0 PID 78 failed/forbidden
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.extractPropertyElements(ManagementClientImpl.java:986) ~[?:?]
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.lambda$readProperty$0(ManagementClientImpl.java:570) ~[?:?]
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.waitForResponses(ManagementClientImpl.java:905) ~[?:?]
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.readProperty(ManagementClientImpl.java:568) ~[?:?]
    at tuwien.auto.calimero.mgmt.ManagementClientImpl.readProperty(ManagementClientImpl.java:535) ~[?:?]
    at org.openhab.binding.knx.internal.client.DeviceInfoClientImpl.lambda$2(DeviceInfoClientImpl.java:107) ~[?:?]
    at org.openhab.binding.knx.internal.client.DeviceInfoClientImpl.readFromManagementClient(DeviceInfoClientImpl.java:56) ~[?:?]
    at org.openhab.binding.knx.internal.client.DeviceInfoClientImpl.readDeviceProperties(DeviceInfoClientImpl.java:105) ~[?:?]
    at org.openhab.binding.knx.internal.client.DeviceInspector.readDeviceProperties(DeviceInspector.java:108) ~[?:?]
    at org.openhab.binding.knx.internal.client.DeviceInspector.readDeviceInfo(DeviceInspector.java:88) ~[?:?]
    at org.openhab.binding.knx.handler.AbstractKNXThingHandler.describeDevice(AbstractKNXThingHandler.java:89) ~[?:?]
    at org.openhab.binding.knx.handler.AbstractKNXThingHandler.lambda$0(AbstractKNXThingHandler.java:153) ~[?:?]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
    at java.lang.Thread.run(Thread.java:748) [?:?]

Let me know if I can do anything to resolve this…

2

Do you use Router or Tunnel mode?

in Tunnel mode, the interface will provide a PA - Physical Address (not GA) to you, so you can leave this unset if you don’t know it.

In Router mode, just make sure that you are using a free PA.

PA format: x.y.z
GA format: x/y/z

3

Running in Tunnel mode. I’m using a GIRA KNX IP Router. So I guess I can use both if needed?
Not sure if I would gain anything with the fetch option? Is it worth the effort to activate this properly?

I’ve just disabled all ‘fetch’ options. And the ‘error’ seems to be gone…

4

I don’t know for sure… I have this parameter disabled.
It seems that it only pulls some basic info from the device. it’s not clear to me if it will grab a list of GAs… even if it does bring a list of GAs: I don’t need that info since I have my ETS to look up my configs.

Yes, you could use both options with a KNX/IP Router like the GIRA.

1 Like