Errors from keep-alive messages flooding the log

[LauOVin]

Hello

I have a TCP listener channel, that receives messages directly from a Wi-Fi medical device.

Every 5 minutes the device sends a keep-alive message, that does not comply with the MLLP transmission mode, which then creates an error in the log:

[2022-06-22 10:00:07,093]  ERROR  (com.mirth.connect.connectors.tcp.TcpReceiver:746): Error receiving message (TCP Listener "Source" on channel c3109784-eab2-4439-8620-01eb3be00d1c).
com.mirth.connect.model.transmission.framemode.FrameStreamHandlerException: End of message bytes (<FS><CR>) not detected. Last bytes received: é)
	at com.mirth.connect.model.transmission.framemode.FrameStreamHandler.read(FrameStreamHandler.java:221)
	at com.mirth.connect.connectors.tcp.TcpReceiver$TcpReader.readBytes(TcpReceiver.java:813)
	at com.mirth.connect.connectors.tcp.TcpReceiver$TcpReader.call(TcpReceiver.java:620)
	at com.mirth.connect.connectors.tcp.TcpReceiver$TcpReader.call(TcpReceiver.java:511)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

I tried to make a filter that rejects messages that does not have a HL7 MSH field, but it doesn't work. I think it is because the keep-alive message is not shown in the message statistics at all.

I tried to change transmission mode to Basic TCP, and was able to see one of these keep-alive messages in the message statistics:

I have tried several different encodings, but it doesn't make the keep-alive message readable.

Do anyone have a tip to how I can stop the log from getting flooded by these errors?

[LauOVin]

Spoke with the technical support from the vendor. Keep-alive messages was caused by the device trying to synchronize time. By enabling NTP in the device configuration, and setting a server hostname, the keep-alive messages to Mirth stopped.