We did some checking and your controller does quite a bit of thrashing (connecting/re-connecting) which created that “other” type watering. We actually have firmware code that will send any completed schedule data if the controller is offline during water completion. If we didn’t have that you would have “lost” that watering
This also explains the choppy event history.
Are you using a range extender, do you have a vanilla network setup or something elaborate?
Also might start by updating the firmware on your router, that actually solves a lot of these issues.
Here is some of the sausage.