Those ping results are very bad. I suspect a network problem.
Here are some ping results from A RPi4b TO RPi4B. Code: -------------------- PING 192.168.1.51 (192.168.1.51): 56 data bytes 64 bytes from 192.168.1.51: seq=0 ttl=64 time=12.515 ms 64 bytes from 192.168.1.51: seq=1 ttl=64 time=3.050 ms 64 bytes from 192.168.1.51: seq=2 ttl=64 time=2.964 ms 64 bytes from 192.168.1.51: seq=3 ttl=64 time=2.748 ms 64 bytes from 192.168.1.51: seq=4 ttl=64 time=2.574 ms 64 bytes from 192.168.1.51: seq=5 ttl=64 time=2.317 ms 64 bytes from 192.168.1.51: seq=6 ttl=64 time=2.047 ms 64 bytes from 192.168.1.51: seq=7 ttl=64 time=2.050 ms 64 bytes from 192.168.1.51: seq=8 ttl=64 time=2.903 ms 64 bytes from 192.168.1.51: seq=9 ttl=64 time=2.704 ms 64 bytes from 192.168.1.51: seq=10 ttl=64 time=2.470 ms 64 bytes from 192.168.1.51: seq=11 ttl=64 time=3.359 ms 64 bytes from 192.168.1.51: seq=12 ttl=64 time=2.916 ms 64 bytes from 192.168.1.51: seq=13 ttl=64 time=2.974 ms 64 bytes from 192.168.1.51: seq=14 ttl=64 time=3.010 ms 64 bytes from 192.168.1.51: seq=15 ttl=64 time=2.650 ms 64 bytes from 192.168.1.51: seq=16 ttl=64 time=2.472 ms 64 bytes from 192.168.1.51: seq=17 ttl=64 time=2.322 ms 64 bytes from 192.168.1.51: seq=18 ttl=64 time=3.139 ms 64 bytes from 192.168.1.51: seq=19 ttl=64 time=2.886 ms --- 192.168.1.51 ping statistics --- 20 packets transmitted, 20 packets received, 0% packet loss round-trip min/avg/max = 2.047/3.203/12.515 ms -------------------- ------------------------------------------------------------------------ Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403 View this thread: http://forums.slimdevices.com/showthread.php?t=114465 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins