While looking into Wombat issue 47 it seems like IoTa is missing messages from MQTT. It could be some pika/async weirdness that isn't coded correctly in IoTa.
The Wombat log claimed all messages over a few hours were sent successfully, but some of these messages did not show up in the IoTa Wombat service log as received.
It might be worth re-writing the Wombat receiving service to use mosquitto_sub and a pipe or similar to create files that are then read into by a python process, similar to how the TTN webhook / processor does it.
While looking into Wombat issue 47 it seems like IoTa is missing messages from MQTT. It could be some pika/async weirdness that isn't coded correctly in IoTa.
The Wombat log claimed all messages over a few hours were sent successfully, but some of these messages did not show up in the IoTa Wombat service log as received.
It might be worth re-writing the Wombat receiving service to use mosquitto_sub and a pipe or similar to create files that are then read into by a python process, similar to how the TTN webhook / processor does it.