KNX read requests times out

[Patrik Åkerfeldt]

When the kxn binding sends read requests to my items I almost always get timeout responses. Like this:

22:32:11.219 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Heating_Bathroom

22:32:11.319 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Temperature_Bedroom2

22:32:21.321 WARN  o.o.b.k.i.bus.KNXBinding[:450] - Cannot read value for item 'Temperature_Bedroom2' from KNX bus: timeout waiting for group read response

22:32:21.371 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Temperature_GuestRoom

22:32:31.372 WARN  o.o.b.k.i.bus.KNXBinding[:450] - Cannot read value for item 'Temperature_GuestRoom' from KNX bus: timeout waiting for group read response

22:32:31.423 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Temperature_Livingroom

I'm using eibd which connects to my KNX/IP router.

It doesn't have any problems receiving values sent directly from the different KNX devices though.

Any clues?

/på

[honkt...@gmail.com]

Hi,

I sometimes experience this tho very occasionally.

I'm using eibd connected by USB to KNX so a sligthly different setup.

May I ask why you're using openhab+eibd+ip-router and not openhab+ip-router?

Thanks,

Sascha

[Kai Kreuzer]

Are you sure that the "r"ead flags for these group addresses are set on your devices?

Regards,

Kai

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/groups/opt_out.

[Patrik Åkerfeldt]

(I think I responded incorrectly so here's my response again)

Yes, I'm positive about the read flags. I can read the group addresses from ETS directly. So they do respond from there.

The reason I use eibd is because I never got the "router" functionality of the IP router to function correctly (probably due to me not understanding how it's supposed to work). But I'd love to ditch eibd if I could and knew how to. Will dig into that as well later.

/på

[Patrik Åkerfeldt]

I managed to get the ROUTER working, using these settings:

# KNX gateway IP address

# (optional, if serialPort or connection type 'ROUTER' is specified)

#knx:ip=192.168.1.2

# KNX IP connection type. Could be either TUNNEL or ROUTER (optional, defaults to TUNNEL)

# Note: If you cannot get the ROUTER mode working (even if it claims it is connected),

# use TUNNEL mode instead with setting both the ip of the KNX gateway and the localIp.

knx:type=ROUTER

# KNX gateway port (optional, defaults to 3671)

#knx:port=

# Local endpoint to specify the multicast interface, no port is used (optional)

knx:localIp=192.168.1.2

# Serial port of FT1.2 KNX interface (ignored, if ip is specified)

# Valid values are e.g. COM1 for Windows and /dev/ttyS0 or /dev/ttyUSB0 for Linux

#knx:serialPort=

# Pause in milliseconds between two read requests on the KNX bus during

# initialization (optional, defaults to 50)

#knx:pause=

# Timeout in milliseconds to wait for a response from the KNX bus (optional,

# defaults to 10000)

#knx:timeout

# Number of read retries while initialization items from the KNX bus (optional,

# defaults to 3)

#knx:readRetries

and I also ran sudo route add 224.0.23.12 dev eth0

But I still get some timeouts, here's one example:

21:41:41.356 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item SetPoint_Actual_Bedroom2

21:41:41.409 INFO  runtime.busevents[:42] - SetPoint_Actual_Bedroom2 received command 20.0

21:41:41.458 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Heating_Bedroom1

21:41:41.510 INFO  runtime.busevents[:42] - Heating_Bedroom1 received command 0

21:41:41.559 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Heating_Kitchen

21:41:41.610 INFO  runtime.busevents[:42] - Heating_Kitchen received command 0

21:41:41.659 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Temperature_Kitchen_Passage

21:41:48.973 INFO  runtime.busevents[:42] - Temperature_Bathroom received command 22.2

21:41:51.534 INFO  runtime.busevents[:42] - Temperature_Entrance received command 21.04

21:41:51.660 WARN  o.o.b.k.i.bus.KNXBinding[:450] - Cannot read value for item 'Temperature_Kitchen_Passage' from KNX bus: timeout waiting for group read response

21:41:51.710 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Heating_GuestRoom

21:41:51.761 INFO  runtime.busevents[:42] - Heating_GuestRoom received command 15

21:41:51.811 DEBUG o.o.b.k.i.bus.KNXBinding[:445] - Sending read request to KNX for item Kitchen_TableLamp

Any help is much appreciated!

/på

[andrea....@gmail.com]

Sometime I experience the same problem.
In my set-up I've eibnetmux.
When this happens all the applications using calimero library start mis-be having
I think the problem is in calimero library, because the problem disappear restarting the application without restarting eibnetmux.
Looking with bus monitor when the problem is in place, I was seeing the responses first and the timeout after.
I promised my self several time to have a look to calimero.
Regards,
Andrea

[Patrik Åkerfeldt]

Has anyone reached out to the authors of Calimero about this?

/på

[andrea....@gmail.com]

Dear Patrik,

openhab guys created a git repository on github (https://github.com/openhab/calimero), I've my clone at https://github.com/jock71/calimero

Last time I did a fix/enhancement it has been integrated by openhab team.

Calimero guys does not seem to be actively maintaing the library (or at least I was not able to find it).

What I found looking to the code is a potential race condition in ProcessCommunicatorImpl class of tuwien.auto.calimero.process package.

I'm not able to replicate the problem when the debugger is attached, but I plan to make some change and give it a try.

Any feedback, contribution is welcome,

            Andrea

[Patrik Åkerfeldt]

Good to hear. Let us know if you find anything!

/på

[mo...@gmx.de]

Hi,
some time ago I figured out that the problems appear as soon AS
I program a Device with ETS. A touch in the knx-binding reestablishes
the connection, and receive works again.
I also use a setup with eibd. Misterhouse on the same machine had never
problems with that.
My 2 cent.
-Steffen