That's...really weird. The criteria checks for primary stars that have "WasDiscovered" values of 0 (StellarMass x WasDiscovered=0 AND DistanceFromArrivalLS=0). I wonder if those systems were never "discovered" per se, and therefore that value is still 0 in the journal. I have been to Sol and Sirius, though I don't remember when, and they don't show up on my list. So that makes it a little weirder. I do, however, have
Sinann and
Taygeta (they being the closest non-forged systems to where Sol and Sirius would be) listed as undiscovered, both populated and listed on EDSM since 2014. So yeah, somehow it gets triggered on populated systems. I don't think I've seen it trigger on discovered systems in the black since I've learned that a blank scanner upon arrival in a system means it hasn't been discovered, though. To me, that's where it counts.
I found my journal data for
Epsilon Eridani, where I apparently scanned the Nav Beacon:
{ "timestamp":"2019-08-18T19:31:17Z", "event":"Scan", "ScanType":"NavBeaconDetail", "BodyName":"Epsilon Eridani", "BodyID":0,
"DistanceFromArrivalLS":0.000000, "StarType":"K", "Subclass":2,
"StellarMass":0.750000, "Radius":570039104.000000, "AbsoluteMagnitude":6.241776, "Age_MY":11988, "SurfaceTemperature":4908.000000, "Luminosity":"V", "RotationPeriod":371628.343750, "AxialTilt":0.140543, "Rings":[ { "Name":"Epsilon Eridani A Belt", "RingClass":"eRingClass_MetalRich", "MassMT":1.1758e+14, "InnerRad":9.5588e+08, "OuterRad":2.1924e+09 } ],
"WasDiscovered":false, "WasMapped":false }
There you have it. Somehow nav beacons don't think their systems have been discovered. Or maybe they never were "discovered" by a player, being populated at game launch. I'd be curious to know if a honk or a system that wasn't populated at launch yields the same result, but I don't know the last populated system I honked, or what systems fit the latter criteria, so I won't go digging for it.