I think it would be really neat to support JS8Call in a similar way to the offline EAS integration - allowing specific callsigns or preables to trigger forwarding of messages from JS8Call out over the mesh.
I think it would be really neat to support JS8Call in a similar way to the offline EAS integration - allowing specific callsigns or preables to trigger forwarding of messages from JS8Call out over the mesh.
<!-- github-sync-id:3104428170 -->
Example here for wsjt
https://github.com/ckuhtz/ham/tree/main/wsjtx
https://github.com/ckuhtz/ham/blob/main/mcast/recv_decode.py
Use case here
https://github.com/dslotter/wsjtx_to_n3fjp/blob/master/wsjtx_to_n3fjp.py
Example from source tree for messages
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/UDPExamples/BeaconsModel.hpp
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/UDPExamples/BeaconsModel.cpp
<!-- github-comment-id:3456854609 -->
Something like two new functions in modules/radio.py
Ideally they have a filter for a list of "watched call signs"
Have a UDP listener to grab them both and parse them? Be sure to to limit brodcast ip and port only to the services here
We also need to await like we do for monitoring Hamlib
A new async task for the listener added to main in mesh_bot.py
Something like two new functions in modules/radio.py
Ideally they have a filter for a list of "watched call signs"
Have a UDP listener to grab them both and parse them? Be sure to to limit brodcast ip and port only to the services here
We also need to await like we do for monitoring Hamlib
A new async task for the listener added to main in mesh_bot.py
<!-- github-comment-id:3457145782 -->
I think it would be really neat to support JS8Call in a similar way to the offline EAS integration - allowing specific callsigns or preables to trigger forwarding of messages from JS8Call out over the mesh.
Give this a test? It's still fresh might need a refactor but I'm wondering if it detects
> I think it would be really neat to support JS8Call in a similar way to the offline EAS integration - allowing specific callsigns or preables to trigger forwarding of messages from JS8Call out over the mesh.
Give this a test? It's still fresh might need a refactor but I'm wondering if it detects
https://github.com/SpudGunMan/meshing-around/pull/246
<!-- github-comment-id:3458124642 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I think it would be really neat to support JS8Call in a similar way to the offline EAS integration - allowing specific callsigns or preables to trigger forwarding of messages from JS8Call out over the mesh.
Example here for wsjt
https://github.com/ckuhtz/ham/tree/main/wsjtx
https://github.com/ckuhtz/ham/blob/main/mcast/recv_decode.py
Use case here
https://github.com/dslotter/wsjtx_to_n3fjp/blob/master/wsjtx_to_n3fjp.py
Example from source tree for messages
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/UDPExamples/BeaconsModel.hpp
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/UDPExamples/BeaconsModel.cpp
Js8Call method
https://github.com/simplyequipped/pyjs8call/blob/main/pyjs8call/js8call.py
https://github.com/simplyequipped/pyjs8call/tree/main/pyjs8call
Details on js8call
https://github.com/js8call/js8call/tree/main
Something like two new functions in modules/radio.py
Ideally they have a filter for a list of "watched call signs"
Have a UDP listener to grab them both and parse them? Be sure to to limit brodcast ip and port only to the services here
We also need to await like we do for monitoring Hamlib
A new async task for the listener added to main in mesh_bot.py
Wsjt specs in a different project https://github.com/MarcFontaine/wsjtx-udp
Give this a test? It's still fresh might need a refactor but I'm wondering if it detects
https://github.com/SpudGunMan/meshing-around/pull/246
CoPilot is crazy. Thanks @SpudGunMan for looking at this!!