KNX Status updates at startup

Hi There

Am having a few new issues with my KNX setup. Things were all working fine until a recent update (although I’ve made some changes, so it could be my bad too!)

I’ve got a number of KNX lighting group addresses setup. But when I start OpenHab it is not setting the current status of all my group addresses properly.

All the group addresses are working correctly. I can turn lights on and off. But their status at startup is not correct. It is reading the status ok once everything has started - as when i use a physical KNX switch on my wall, the status updates on the Openhab Basic UI.

Messages in my log file are as follows:

2016-12-01 10:03:28.132 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'Light_GF_Kitchen_Island' from KNX bus: timeout waiting for group read response: timeout
2016-12-01 10:03:28.135 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '1/2/19' = '2'
2016-12-01 10:03:38.188 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'Light_GF_Table' from KNX bus: timeout waiting for group read response: timeout
2016-12-01 10:03:38.189 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '1/2/29' = '2'
2016-12-01 10:03:48.242 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'Light_GF_Kitchen_LED' from KNX bus: timeout waiting for group read response: timeout
2016-12-01 10:03:48.243 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '1/2/18' = '2'
2016-12-01 10:03:58.302 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'Light_GF_Lounge_Side' from KNX bus: timeout waiting for group read response: timeout
2016-12-01 10:03:58.303 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '1/2/13' = '2'
2016-12-01 10:04:08.356 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'Light_FF_Stairs' from KNX bus: timeout waiting for group read response: timeout
2016-12-01 10:04:08.357 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '1/2/8' = '2'

And my item file for KNX looks like this:

Switch Light_GF_Kitchen_LED 	"LED"    (Kitchen, Lights) [ "Lighting" ]    {knx="1/1/18+<1/2/18"} 
Switch Light_GF_Kitchen_Island 	"Island" (Kitchen, Lights) [ "Lighting" ]    {knx="1/1/19+<1/2/19"} 
Switch Light_GF_Lounge_Side     "Lounge" (Living,Lights)   [ "Lighting" ]    {knx="1/1/13+<1/2/13"}
Switch Light_GF_Table           "Table"  (Dining,Lights)   [ "Lighting" ]    {knx="1/1/29+<1/2/29"}

The only real thing I have changed is to add the tag [“Lighting”] to the item so I can get the Amazon Echo Hue emulator working (Which is working well by the way!)

@Dim - you have given me some fantastic KNX support previously, wondered if you know whats going on and what I’ve missed!

Pete

Hi @PeteW,

First, check if the Status GAs are allowed to pass the IP Router Filter Table in the ETS configuration of the Router (link them to the dummy App to allow them to be routed).
The command GAs look like they work fine and that’s why your OH2 shows the updates after startup (OH2 receives the command also and then shows the updates).

BR,
Dim

Thanks Dim. Just checked the IP Router Filter Table. Had a couple of status items missing, so updated. but still getting the warnings. How do i check the Status GAs are allowed to pass the router? Is it just by updating the IP Router with the right filter table? ie, upolading the app via ETS once I’ve linked the GAs to the dummy Openhab App)

Correct. Just link the GAs to the dummy App and reprogram the Router via ETS. This will modify the Filter Table.

Hmm… I don’t see why the telegrams for the autorefresh are timing out… If the Router is configured correctly to route the telegrams for these Status GAs, OH2 should get the responses and update the status of the knx items… (this works fine in my installation)

Try to simplify your items file a bit for troubleshooting purposes:
configure only one (1) simple (without many flags etc) knx item with Status GA and make sure that this GA is linked to the dummy app in ETS
Try this out and check the logs with (in karaf console):

log:set TRACE org.openhab.binding.knx
log:set TRACE tuwien.auto.calimero

BR,
Dim

thanks, I’ll give that a go tonight. It could be the [label] i’ve added. Process of elimination i think…

Have simplified things down to a single GA, and got rid of the [tag].

Switch Light_GF_Kitchen_Island 	"Island" (Kitchen, Lights)    {knx="1/1/19+<1/2/19"}

Still getting the same errors, can’t see from the log what’s up…any ideas?

20:43:57.589 [INFO ] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: send message to 1/2/19, wait for confirmation
20:43:57.590 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: cEMI L-Data.ind from 0.0.1 to 1/2/19, low priority hop count 6 tpdu 00 00
20:43:57.590 [DEBUG] [tuwien.auto.calimero                ] - KNXnet/IP Routing 224.0.23.12:3671: add to multicast loopback frame buffer: L-Data.ind from 0.0.1 to 1/2/19, low priority hop count 6 tpdu 00 00
20:43:57.591 [DEBUG] [tuwien.auto.calimero                ] - KNXnet/IP Routing 224.0.23.12:3671: sending cEMI frame seq 0, non-blocking, attempt 1 (channel 0) 06 10 05 30 00 11 29 00 bc e0 00 01 0a 13 01 00 00
20:43:57.592 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: send to 1/2/19 succeeded
20:43:57.593 [DEBUG] [tuwien.auto.calimero                ] - process 224.0.23.12:3671: sent group read request to 1/2/19
20:43:57.594 [DEBUG] [tuwien.auto.calimero                ] - KNXnet/IP Routing 224.0.23.12:3671: discard multicast loopback cEMI frame: L-Data.ind from 0.0.1 to 1/2/19, low priority hop count 6 tpdu 00 00
20:43:58.000 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
20:43:58.000 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: indication from 1.0.202
20:43:58.001 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 2/1/7
20:43:58.970 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
20:43:58.970 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: indication from 1.0.201
20:43:58.971 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 2/1/0
20:44:00.620 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
20:44:00.620 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: indication from 1.0.103
20:44:00.621 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 2/1/81
20:44:00.840 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: indication from 1.0.208
20:44:00.840 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
20:44:00.841 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 2/0/16
20:44:00.860 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
20:44:00.860 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: indication from 1.0.208
20:44:00.861 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 2/1/54
20:44:01.965 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
20:44:01.965 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: indication from 1.0.201
20:44:01.967 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 2/1/0
20:44:03.415 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
20:44:03.415 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: indication from 1.0.204
20:44:03.417 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 2/0/5
20:44:03.435 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
20:44:03.437 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 2/1/26
20:44:03.438 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: indication from 1.0.204
20:44:05.510 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: indication from 1.0.211
20:44:05.512 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
20:44:05.513 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 2/0/12
20:44:06.615 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
20:44:06.616 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 2/0/1
20:44:06.618 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: indication from 1.0.206
20:44:06.635 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.224.0.23.12:3671: indication from 1.0.206
20:44:06.636 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
20:44:06.638 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 2/1/40
20:44:07.590 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'Light_GF_Kitchen_Island' from KNX bus: timeout waiting for group read response: timeout

I appreciate it’s a long time since this post was last responded to - do you have the Read flags set for your your feedback/status objects in ETS? If the read flag is not set you can ask for the value but the group object will not give it.

thanks, will take a look at that. Its still an issue in openhab. Although i am also using a Gira homeserver thats working ok and i think that needs the read flag set.

Yes - if your Homeserver is getting these values then I expect the Read flag will be set. Worth a try!