MQTTMessageProcessorEndpoint$mqttCallback: Connection Lost
I'm noticing this java error, not sure whether it's related to ot-recorder or mosquitto
2025-09-26 15:46:25.048 I [DefaultDispatcher-worker-7] MessageProcessor$processIncomingMessage: Contact owntracks/eric/pixel9 moved to **.84518909,**.375854842500001 at 1758894073
2025-09-26 15:46:36.661 E [MQTT Rec: redfin] MQTTMessageProcessorEndpoint$mqttCallback: Connection Lost
Connection lost (32109) - java.io.EOFException
at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:261)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:524)
at java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:348)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
at java.lang.Thread.run(Thread.java:1119)
Caused by: java.io.EOFException
at java.io.DataInputStream.readByte(DataInputStream.java:275)
at org.eclipse.paho.client.mqttv3.internal.wire.MqttInputStream.readMqttWireMessage(SourceFile:14)
at org.eclipse.paho.client.mqttv3.internal.CommsSender.run(SourceFile:88)
... 6 more
It repeats every few minutes.
This is Android 14 device (same problem with another device and Android16)
moved to "Android"
The title on your issue says "MQTTMessageProcessorEndpoint", so it's MQTT related, i.e. it cannot be the Recorder.
The title on your issue says "MQTTMessageProcessorEndpoint", so it's MQTT related, i.e. it cannot be the Recorder.
I was about moving it myself :)
This issue is usually because the app loses its TCP connection (with keepalives) to the broker. There's quite a few things that could cause this to happen, from flakey networks though to your OS not scheduling CPU time for OT to get the keepalive packets out and onto the wire.
You've not mentioned what make/model device you're using, nor whether you've got the battery optimizations disabled for OT. That'd help pin down what's going on.
Marking issue with request for more data as stale, due to no updates.