Chris,
It might be that JMRI closes the connection when it times out.
The log you sent before had these lines:
> 2024-09-03T19:03:14,734
mqtt.MqttAdapter????????????????????? ERROR - Can't publish :?
[AWT-EventQueue-0]
> org.eclipse.paho.client.mqttv3.MqttException: Timed out
waiting for a response from the server
So it could be that the broker gets unresponsive due to high
volume and that JMRI then closes the connection. But that's a
guess that I'm doing.
Daniel
On 2024-09-05 12:25, Chris Holden
wrote:
toggle quoted message
Show quoted text
Hi Daniel - it appears to be JMRI that closed the connection
-
?
2024-09-03T19:03:14: Client TheLoftJMRI8EB8A1FEM closed its
connection.
?
There had been a high volume of messages in the minutes
leading up to this disconnection - like I mentioned earlier, an
RFID reader was flooding with the same ID. It also looks like I
restarted an Arduino during those few minutes which resulted in
a few sensor updates all going to JMRI at once.
?
Mosquitto log files are big! I've uploaded the logs from
19:00 until 19:04 (when I shut everything down) in case you want
to sift through it!
?
192.168.1.29 is the IP of the PC that runs JMRI, has
mosquitto installed on it and also runs a couple of c# apps that
also publish to MQTT. It looks from the logs like they're not
particularly efficient and are constantly connecting /
disconnecting from MQTT - I might have to have a look at that.
?
As JMRI and mosquitto are on the same PC, the log times match
up exactly.
?
?
Thanks,
Chris
?
?
