Oh, I see now why this is hard. Need to do stuff without delay() so the webserver can continue to operate.
No response. Next up is to swap in the kiss3 package (see if it basically works) and then try the async method, I guess. https://github.com/python-aprs/kiss3/blob/main/examples/tcp_async.py
About the connection query issue: I asked on a kiss3 GitHub issue because that might be under more active development. https://github.com/python-aprs/kiss3/issues/9
Might try to drop this from 1 to None as in the example at https://github.com/python-aprs/kiss3/blob/main/examples/tcp_send_recv.py:
for frame in ki.read(min_frames=1):
To test this, I can write up a test connection to run locally, establish the connection, the unplug the network and see what happens. Plug back in to see if reconnect is successful.
I tried…
Following from experiments around W1CDN/aprs_tool#30 (comment), maybe the issue is partly on the direwolf side? Sometimes it stops responding to connections…
Once I figure out how to get the data out of above, I think I can check the connection every so often using one of these solutions: https://stackoverflow.com/questions/474528/how-to-repeatedly-exec…
Running interactively, you can get some info from the ki object:
>>> ki = aprs.TCPKISS(host="localhost", port=8001)
>>> ki
TCPKISS(_protocol=None)
>>> ki.start()
>>> ki
TCPKISS(_protoc…
Still thinking about where this message might be coming from, and how to check the connection periodically.
Something with…
If packet is an object, aprs.fi link should track the object name, not the station name (or have a link for each?)
Might consider using aprs3 package instead? https://github.com/python-aprs/aprs3