In cases where the location of a digipeater isn't known, skip that digipeater line but add a "?" on the line, indicating there is a hop we can't see the location of.
It might be time to use sqlalchemy or some other way to abstract the database calls. My first pass is pretty ugly.
For example, I should be able to arbitrarily select on ANY field.
I wonder if using aprs_api/packets/<callsign-ssid> works better on the back end than aprs_api/packets/?from=<callsign-ssid>.
This seems to be the path field we get in the current version.
467ec11522
Merge pull request 'Add background KISS connection, log frames to database' (#20) from add-kiss into main
I'll be debugging packets forever, I think!
{'raw': 'FGFFLS>APRS,TCPIP,W1CDN-1*:;FGFFLS2AA*170815z4753.10N\\09657.90Ww FLOOD }k0I8Pdd`P:88P{G2AAA', 'from': 'FGFFLS', 'to': 'APRS', 'path':…
Drop this stuff into config.ini:
MYCALL = os.environ.get("MYCALL", "W1CDN")
KISS_HOST = os.environ.get("KISS_HOST", "192.168.0.30")
KISS_PORT = os.environ.get("KISS_PORT", "8001")
Progress on #20 means that one KISS connection is always active for receive. Need to think about how to best use the connection so we don't go over the maximum of three KISS clients (default…