Well, the problem is that a logging entry is created with the same error every 1 or 2 seconds. So even if there is no real problem, it completely destroys the logging, because all other useful log messages are flushed out by this flood of logging.
It is being logged at maximum every 2 seconds. So in 1 hour that is 30 x 60 = 1800 log messages. In 24 hours it's 43000 log messages. So in 1 day you can't even see anything in the logging anymore, because it's full of this message.
I've checked all the possibly related messages, but there's nothing that points to a problem source that I can investigate. And I'm a seasoned software developer, unable to diagnose this issue. Imagine what a regular computer user's chances are of diagnosing this.
The error message should simply be improved: it should either clarify that there is no real problem, and then it shouldn't be an error level message, but a warning, and even then it should identity the source device, or if there is a real problem, it should also make note of the device causing the issue. So my request is to relay this to the software developers that built this and improve the error message, and also do something about the frequency of the error message. Like if this is a problem at some point in time, why is there a need to log the exact same thing 2 seconds later?