Connected to myself messages are harmless, but might point to a not optimal configuration. It usually happens when there are multiple Syncthing clients behind the same router and port-forwarding is setup for one (some) of these, while everyone is listening on port 22000. So if A has the port forward and tries to connect to B via their global IP, that happens to end up at the port forward back to A. I myself fix that by setting non-standard listening ports on Syncthing clients which get port forwards. Discovery could probably be a bit smarter by filtering addresses which are known to point at itself, but as it’s not harmful, hardly worth the effort.