BUT according to your log... Bhutan-1 is responding to Wide1-1, not ARISS / RS0ISS / et al...
It is not responding, but it is generating a Beacon from Bhutan-1:
1:Fm BIRDBT To APTT4 Via WIDE1-1 <UI R Pid=F0 Len=50> [16:28:38R] [-++] HELLO! THIS IS APRS-DIGIPEATER OF BHUTAN-1 CUBESAT
My APRS recommendation for ALL APRS satellites since 2001 is that they should support these three aliases: Via ARISS - (for backward compatibility with ARISS users) Via APRSAT - (for ALL APRS satellites) Via WIDEn-N - (for those that forget to switch from Terrestrial mode)
And, that simple periodic health telemetry from such satellites may be sent "via APRSAT" so that they can be heard beyond the horizon if there is another APRS satellite that is closer.
Sending these spacecraft packets via WIDE1-1 is not good for the channel. It has the potential to generate footprint QRM anywhere in the world where a user may have their radios set to also be a fill in digipeater when used terrestrially. Such radios will key up on receipt of this packet and block the satellite for a full packet period. Thus reducing user throughput.
All it takes is for one person in the whole country to have his rig set for fill-in digi, and this ueless extra WIDE1-1 will add this useless QRM on the uplink over that entire footprint. And no one except someone living within a few miles of this mistake will ever be able to detect it. Though it impacts everyone.
I was certain I had published these settings as APRS SPACE GOSPEL, but just now I looked over all my aprs satellite p[ages and cannot find it anywhere except in the detail settings for each of my satellites. I'm sure it is in an AMSAT paper somewhere...
Bob