Niko Nelissen

Hi RyanE, FYI, it took some time to get our Gira KNX IP gateway (2168 00) replaced with a Gira KNX IP router (2167 00), but indeed it seems that solved the problem. Many thanks for your advice ! Best, Niko

Hi, We have our Control4 system for over 8 years now, and sometimes it looses connection with KNX, which means we can no longer control our lights with e.g. the Control4 mobile app. Sometimes the connection is fine for weeks, but most of the time we have to reset the connection daily or more. We added a "reset" button in the app which deconnects + wait 5 sec + connects again with KNX. We had this issue when we were using the Tisco KNX driver and recently our Control4 installer/dealer replaced this with the Control4 KNX driver (Control4 KNX Master 'Network' Driver, Version 36 ) and we still have the same issue. I believe the IP gateway has been replaced a few years ago as well. Below is the log of what happens when we dim a light and the connection is lost. Does anyone have an idea what could be causing this ? Thanks ! Niko ------ DEBUG OUTPUT WHEN DIMMING LIGHT WHILE CONNECTION IS LOST: <Proxy SEND_TO_KNX (DATA_POINT_TYPE: "DPT_5", VALUE: "115", GROUP_ADDRESS: "0/3/1") Queue> KNX Write Request [0/3/1] VALUE: 115 CMD: [02 00 80 73] gTimeoutTimer expired - Did not receive ACK, try resending gTimeoutRetries = 1 ... (5 retries) Connection Check OK gTimeoutTimer expired - Did not receive ACK, try resending Maximum number of retries reached, resetting the queue ALL OUTPUT WHEN DIMMING LIGHT WHILE CONNECTION IS LOST: <Proxy SEND_TO_KNX (DATA_POINT_TYPE: "DPT_5", VALUE: "163", GROUP_ADDRESS: "0/3/1") Queue> KNX Write Request [0/3/1] VALUE: 163 CMD: [02 00 80 A3] -----> TUNNELLING_REQUEST 06 10 04 20 00 16 04 6D 68 00 11 00 BC E0 00 00 03 01 02 00 80 A3 gQueueTimer expired - OK to Send Next Command gTimeoutTimer expired - Did not receive ACK, try resending gTimeoutRetries = 1 -----> TUNNELLING_REQUEST 06 10 04 20 00 16 04 6D 69 00 11 00 BC E0 00 00 03 01 02 00 80 A3 gQueueTimer expired - OK to Send Next Command -----> CONNECTIONSTATE_REQUEST 06 10 02 07 00 10 6D 00 08 01 C0 A8 0A 15 83 2E <----- CONNECTIONSTATE_RESPONSE [109] 06 10 02 08 00 08 6D 00 gTimeoutTimer expired - Did not receive ACK, try resending gTimeoutRetries = 2 gQueueTimer expired - OK to Send Next Command ... Maximum number of retries reached, resetting the queue OUTPUT WHEN CONNECTION IS WORKING FINE: <Proxy SEND_TO_KNX (DATA_POINT_TYPE: "DPT_5", VALUE: "199", GROUP_ADDRESS: "0/3/1") Queue> KNX Write Request [0/3/1] VALUE: 199 CMD: [02 00 80 C7] <----- TUNNELLING_ACK [110] 06 10 04 21 00 0A 04 6E A9 00 -----> SendKNXTunnellingAck() -----> TUNNELLING_REQUEST 06 10 04 20 00 16 04 6E A9 00 11 00 BC E0 00 00 03 01 02 00 80 C7 <----- TUNNELLING_REQUEST [110] 06 10 04 20 00 16 04 6E D6 00 29 00 BC E0 11 06 04 01 02 00 80 C7 DECODE.DPT_5: 02 00 80 C7 -DEV-> SendToDevice(1015 [Spots], DATA_FROM_KNX: (RESPONSE: false, VALUE: "199", GROUP_ADDRESS: "0/4/1") <----- TUNNELLING_REQUEST [110] 06 10 04 20 00 16 04 6E D6 00 29 00 BC E0 11 06 04 01 02 00 80 C7 -----> SendKNXTunnellingAck()