It also could be that you were seeing the digipeater station by vicinity plotting, as documented here:
This is how your station can guess at the location of a station that hasn't sent a position beacon yet. Since digipeaters generally don't move, they don't have to send their position beacon frequently, so if you had just started YAAC up, you would beacon, the digipeater would send your beacon back to you, and YAAC wouldn't know where the digipeater was, so it would make an educated guess, based on all the stations you have heard that used that digipeater as their first relay station (and, at your startup, you might be the only station relayed through that digi that you had heard), . Once the digipeater does send out a position beacon (that you hear), YAAC will use that position instead of the vicinity plotting guess.
And there are some people who operate "stealth" digipeaters that never position-beacon, but only meet their FCC-mandated identification requirements by using UITRACE path editing, so their callsign is inserted into the digipeat path.
You can tell if a digipeater is vicinity-plotted if it uses the green digipeater star icon with a red question mark superimposed on it. A question mark is not a legal symbol overlay, so YAAC uses it to identify "stealth" digipeaters until and unless they send a position report with their proper symbol code.
If you don't like vicinity plotting, you can turn it off in the YAAC expert-mode configuration dialog on the Behavior tab.
Hope that helps.
Andrew, KA2DDO
author of YAAC
________________________________________
From: yaac-users@groups.io <yaac-users@groups.io> on behalf of Brien - KE7WB <ke7wb@...>
Sent: Saturday, February 3, 2024 12:35 AM
I was running an old version. I downloaded the latest version and the digipeter object is no longer showing up next to my station object.
Brien - KE7WB