KM200 binding, logfile contains many entries "Communication is not possible!"

All values are transmitted. It is only a warning, but the logfile contains many entries.


2020-07-16 14:04:12.077 [WARN ] [ab.binding.km200.internal.handler.KM200DataHandler] - Communication is not possible!
2020-07-16 15:01:51.740 [WARN ] [ab.binding.km200.internal.handler.KM200DataHandler] - Communication is not possible!
2020-07-16 15:01:52.840 [WARN ] [ab.binding.km200.internal.handler.KM200DataHandler] - Communication is not possible!
2020-07-16 15:01:53.930 [WARN ] [ab.binding.km200.internal.handler.KM200DataHandler] - Communication is not possible!
2020-07-16 15:02:30.049 [WARN ] [ab.binding.km200.internal.handler.KM200DataHandler] - Communication is not possible!
2020-07-16 15:02:32.189 [WARN ] [ab.binding.km200.internal.handler.KM200DataHandler] - Communication is not possible!
2020-07-16 15:02:33.289 [WARN ] [ab.binding.km200.internal.handler.KM200DataHandler] - Communication is not possible!
2020-07-16 15:28:47.893 [WARN ] [ab.binding.km200.internal.handler.KM200DataHandler] - Communication is not possible!

Does anyone have an explanation for these entries, or is there a way to prevent them?

OH 2.5.6-2
Buderus Logamax Plus, GB172-20 G23
Logamatic RC310, Logamatic web KM200

I have a very similar setup and can confirm those messages. I can find one or two messages per day in my log files. Unfortunately I don’t have a solution, how to get rid of them.

Unfortunately my logfile is flooded with these messages, about 50 per day …
I don’t want to switch off the logging for the binding completely, because i want to be aware of other warnings …

@ludovic_laurent , @oggerschummer, @Markinus maybe you have a tip, or can the problem be solved programmatically?

I also have lots of these warnings every day, but I don’t care - it’s a logfile :wink:


those messages show up whenever the binding has to reconnect with the gateway.
From my experience the KM200 is not one of the most sophisticated devices in this solar system, so the connection gets dropped from time to time.
Be happy that @Markinus did a good job on fixing this as far as possible by implementing reconnection, but you may never get rid of those situations completely.
In the beginning this was much worse, the device crashed and reconnection did not work.

Nevertheless it could be related to network issues, e.g. Wifi connection not being stable.
KM200 uses wired ethernet, but the OH server may not.


Thanks for the feedback, i am of course happy about the great performance of @Markinus to create and maintain this binding :+1:
The connection to the KM200 module is exclusively via ethernet, so the connection should not be the problem.