Closed hemna closed 3 years ago
I think for APRS, the idea was that when sending a message to a specific station, I'd use the SSID of that station instead of broadcasting it, but observing the behaviour of lots of APRS clients, suggests that's not how it's done.
Documentation definitely needs a clean-up. :-)
Okay, so I've re-instated the listen_destinations
feature, but a caveat, it'll break reception of MIC-E traffic if used unless you can find a suitable regular expression pattern to match it, as the destination call-sign is used in MIC-E to encode the position latitude.
I'm struggling with trying to get aioax25 to send me frames from a kiss interface. The README mentions that you can set listen_destinations in the APRSInterface to specify which callsign/ssid to look for. Yet, when passing in listen_destinations dict to APRSInterface I get a failure.
I grepped the repo
I am also calling bind() on the APRSInterface and passing in my callsign and setting regex to false (assuming this means look for an exact match?), but my callback is not getting called when I send an APRS packet.
My callsign is WB4BOR-12 for this instance of aioax25 connected to direwolf. I am using a kenwood TH-D74 to send an aprs message to WB4BOR-12. You can see from the log below that aioax25 gets it, says the frame is for us, but yet then never sends it on to my registered callback from the aprsinterface.bind() call.