[LCN Binding] Module did not respond to command

Add-ons Bindings
1

I’ve been seeing lots of warnings in openhab.log since more than a week. They are of the following types:

[ding.lcn.internal.connection.ModInfo\] - S000M010: Module did not respond to command: R8----1---
[ding.lcn.internal.connection.ModInfo] - S000M201: Failed to receive measurement value: S000M201 THRESHOLD 1: Failed finally after 3 tries
[ding.lcn.internal.connection.ModInfo] - S000M011: Failed to receive status message: Key Locks: Failed finally after 3 tries

I haven’t changed anything - at least as far as I know of.

This is really bad as basically this means that the lcn binding isn’t usable anymore. Commands do not reach the devices, that is e.g. lamps can’t switched on or off. And openHAB isn’t aware of the devices’ statuses.

My interface to LCN is LinHK, which itself still works very well: I can switch all devices (in my linhk-gui) without any issues.

I have tried restarts of the lcn bundle, I changed the timeout in its config, I restarted openHAB but now I have no clue what I can do next.

I am on openHAB 5.4.1.

Has anyone an idea?

2

My openhab.log is also filled with

2026-06-14 21:51:45.625 [WARN ] [ding.lcn.internal.connection.ModInfo] - S000M034: Failed to receive status message: LEDs and Logic: Failed finally after 3 tries
2026-06-14 21:52:15.632 [WARN ] [ding.lcn.internal.connection.ModInfo] - S000M016: Failed to receive status message: LEDs and Logic: Failed finally after 3 tries
2026-06-14 21:52:23.634 [WARN ] [ding.lcn.internal.connection.ModInfo] - S000M034: Failed to receive status message: LEDs and Logic: Failed finally after 3 tries
2026-06-14 21:52:53.640 [WARN ] [ding.lcn.internal.connection.ModInfo] - S000M016: Failed to receive status message: LEDs and Logic: Failed finally after 3 tries
2026-06-14 21:53:01.642 [WARN ] [ding.lcn.internal.connection.ModInfo] - S000M034: Failed to receive status message: LEDs and Logic: Failed finally after 3 tries

I have come to the point to accept them and to migrate from LCN to Shelly step by step. LCN has in IMHO lost the race.

3

LCN works totally fine at my house (for meanwhile 18 years), its reliability is phenomenal.

I suspect the issue somewhere between LinHK and openHAB. For some reason openHAB misses the messages whereas LinHK has no apparent problems.

4

After watching the behaviour very closely I figured that LinHK has issues as well. Which then led me to the conclusion that it might be worth trying to change the USB stick. Yes, and that did the trick.

Sorry for the noise.

5

Sorry again, the issue is still not resolved. It just appeared to be solved for a while plus I was more optimistic than I should have been.

Observation:

  • Stop and starting the lcn bundle does not have any impact.
  • Setting the timeout to a different value makes it work for minutes - at least sometimes.
  • LinHK still works fine.

It would be great if someone could dig deeper into it.

6

Problem seems to be resolved. After testing numerous configurations and tracing the tcp traffic it was probably related to a load issue on the LinHK hardware (FRITZ!Box). Which ist strange as I have rebooted it a couple of times during analysis.

I have been too optimistic before so I’ll wait and see now.