Seems to be missing mqtt messages

[KHouse75]

I'm using mqtt-launcher on Ubuntu 18.04.1 to run a shell script that grabs camera images then e-mails them to me. It works great for the most part but I've been noticing that mqtt-launcher is missing mqtt messages pretty consistently.

If I check the log file, I can see that mqtt-launcher has not detected a message but I can see in my smartthings-mqtt-bridge that the message has been received. I can see in the mosquito logs that mosquito is receiving it from the bridge. I also started an mqtt client on my laptop and subscribed to the message and it's receiving the message no problem as well.

Here's a sample of the log file. You can see at 14:39:08, the contact open was detected and the driveway.sh file was run. However, at 14:36:11, it only caught it as closed which I have no definition for in the config file. An open message was sent and received by other listening mqtt clients.

2019-09-16 14:29:08,993 smartthings/Driveway Motion/contact 0 open
2019-09-16 14:29:08,995 Running t=smartthings/Driveway Motion/contact: ['/bin/sh', '/opt/mqtt-launcher/driveway.sh']
2019-09-16 14:36:11,251 smartthings/Driveway Motion/contact 0 closed
2019-09-16 14:36:11,252 No matching param (closed) for smartthings/Driveway Motion/contact
2019-09-16 14:50:40,542 smartthings/Front Porch Motion Detector/motion 0 inactive

Any ideas what may be causing this?

Edit: I just noticed from the above log that it didn't catch the closed message at 14:29 either. Just the open.

[KHouse75]

Actually, I think the problem is elsewhere. I just noticed that messages are not actually being received by other clients like previously thought. When I refresh the client, the timestamp shown is refresh time, not the actual message time. Closing for now.