Dim
May 25, 2018, 7:58am
1
quick question about KNX2 binding: has the issue with echo telegrams been addressed/fixed in v2 of the KNX binding?
I am experiencing this with a new device that I installed on my KNX bus. Until now, I didn’t pull Number item (with 1 GA) readings from the KNX Bus. I had only Switches and Rollershutters (with many GAs) and never saw echo.
Every GroupValueRead telegram gets a proper GroupValueResponse but then it triggers another GroupValueWrite (this last one is the issue). Of course, with autoupdate="false" this stops but this is not desirable (since I need to persist and display updates on my sitemap)
pinging @Udo_Hartmann
Dim
May 25, 2018, 5:48pm
2
Good news: Seems that the GroupValueWrite is not triggered after a GroupValueResponse with the KNX2 Binding…
Migrating now my KNX1 configs to KNX2 things
==> openhab.log <==
2018-05-25 20:48:09.709 [TRACE] [nx.internal.client.AbstractKNXClient] - Sending a Group Read Request telegram for 3/1/1
2018-05-25 20:48:09.712 [DEBUG] [calimero.link.224.0.23.12:3671 ] - send (wait for confirmation) 1.2.200->3/1/1 L_Data.ind, low priority hop count 6, tpdu 00 00
2018-05-25 20:48:09.715 [TRACE] [p.KNXnet/IP Routing 224.0.23.12:3671] - add to multicast loopback frame buffer: 1.2.200->3/1/1 L_Data.ind, low priority hop count 6, tpdu 00 00
2018-05-25 20:48:09.718 [TRACE] [p.KNXnet/IP Routing 224.0.23.12:3671] - sending cEMI frame seq 0, NonBlocking, attempt 1 (channel 0) 06 10 05 30 00 11 29 00 bc e0 12 c8 19 01 01 00 00
2018-05-25 20:48:09.721 [TRACE] [p.KNXnet/IP Routing 224.0.23.12:3671] - discard multicast loopback cEMI frame: 1.2.200->3/1/1 L_Data.ind, low priority hop count 6, tpdu 00 00
2018-05-25 20:48:09.721 [TRACE] [calimero.link.224.0.23.12:3671 ] - send 1.2.200->3/1/1 succeeded
2018-05-25 20:48:09.723 [TRACE] [ero.process.process 224.0.23.12:3671] - sent group read request to 3/1/1
2018-05-25 20:48:09.811 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Read Response telegram from '1.1.32' to '3/1/1'
2018-05-25 20:48:09.811 [DEBUG] [calimero.link.224.0.23.12:3671 ] - indication 1.1.32->3/1/1 L_Data.ind, low priority hop count 5, tpdu 00 40 40 5d 60 42
2018-05-25 20:48:09.819 [DEBUG] [.internal.handler.DeviceThingHandler] - Thing 'knx:device:bridge:Energy_Meter' received a Group Write telegram from '1.1.32' for destination '3/1/1'
2018-05-25 20:48:09.825 [TRACE] [.internal.handler.DeviceThingHandler] - Thing 'knx:device:bridge:Energy_Meter' processes a Group Write telegram for destination '3/1/1' for channel 'knx:device:bridge:Energy_Meter:CL1'
2018-05-25 20:48:09.828 [TRACE] [g.knx.internal.dpt.KNXCoreTypeMapper] - toType datapoint DPT = 14.019
==> events.log <==
2018-05-25 20:48:09.844 [vent.ItemStateChangedEvent] - CL1 changed from 3.4830000400543213 to 3.4590001106262207
@george.erhan
1 Like
