As @george.erhan wrote, try to delete all KNX related PaperUI based stuff and create a fresh /etc/openhab2/things/KNX.things with minimum configuration options to see if it works.
I can’t pin point the root cause of the problem that you are experiencing …
Here is a TRACE of org.openhab.binding.knx from my setup when I send ON to a Switch from OH2 to KNX:
==> events.log <==
2019-04-04 20:34:03.115 [ome.event.ItemCommandEvent] - Item 'P06_Small_LED' received command ON
==> openhab.log <==
2019-04-04 20:34:03.116 [TRACE] [.internal.handler.DeviceThingHandler] - Handling command 'ON' for channel 'knx:device:GIRA2167:GW90741_4:Ch_42'
2019-04-04 20:34:03.118 [TRACE] [.knx.internal.channel.KNXChannelType] - getCommandSpec testing Keys '[ga]' for command 'ON'
2019-04-04 20:34:03.119 [TRACE] [.knx.internal.channel.KNXChannelType] - getCommandSpec key 'ga' uses expectedTypeClass 'class org.eclipse.smarthome.core.library.types.OnOffType' witch isInstance for command 'ON' and dpt '1.001'
2019-04-04 20:34:03.119 [TRACE] [nx.internal.client.AbstractKNXClient] - writeToKNX groupAddress '1/0/13', commandSpec 'org.openhab.binding.knx.internal.channel.WriteSpecImpl@7902cd65'
2019-04-04 20:34:03.119 [TRACE] [nx.internal.client.AbstractKNXClient] - sendToKNX mappedValue: 'on' groupAddress: '1/0/13'
2019-04-04 20:34:03.120 [DEBUG] [nx.internal.client.AbstractKNXClient] - Wrote value 'ON' to datapoint 'command DP 1/0/13 'knx:ip:GIRA2167', DPT id 1.001, low priority' (0. attempt).
2019-04-04 20:34:03.243 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from '1.1.4' to '1/2/13' with value '[1]'
2019-04-04 20:34:03.244 [DEBUG] [.internal.handler.DeviceThingHandler] - onGroupWrite Thing 'knx:device:GIRA2167:GW90741_4' received a GroupValueWrite telegram from '1.1.4' for destination '1/2/13'
2019-04-04 20:34:03.244 [TRACE] [.internal.handler.DeviceThingHandler] - onGroupWrite Thing 'knx:device:GIRA2167:GW90741_4' processes a GroupValueWrite telegram for destination '1/2/13' for channel 'knx:device:GIRA2167:GW90741_4:Ch_42'
2019-04-04 20:34:03.245 [TRACE] [g.knx.internal.dpt.KNXCoreTypeMapper] - toType datapoint DPT = 1.001
There is a small (but important) difference in the structure of the Channel identification. I have seen this before when using PaperUI and I don’t know if this is a problem or not.
Your log:
Handling command 'ON' for channel 'knx:device:63afe2a3:Test'
My log:
Handling command 'ON' for channel 'knx:device:GIRA2167:GW90741_4:Ch_42'
With text based config, I have 5 sections to fully identify the channel: (1)knx:(2)device:(3)GIRA2167:(4)GW90741_4:(5)Ch_42
With PaperUI based config, I see only 4: (1)knx:(2)device:(3)63afe2a3:(4)Test
It is: (1)knx:(2)device:(3)Bridge:(4)Thing:(5)Channel
which model?
I had trouble setting up my GIRA as a TUNNEL interface but i was successful with ROUTER type of connection (but comms seem to work ok in your setup… you seem to have just a Bridge/Thing/Channel config issue)
