Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Enable Relay to Meshtastic #29

Closed
bmswens opened this issue Jul 18, 2024 · 4 comments
Closed

[Feature Request] Enable Relay to Meshtastic #29

bmswens opened this issue Jul 18, 2024 · 4 comments

Comments

@bmswens
Copy link

bmswens commented Jul 18, 2024

As a user, when I receive data from a TAK server (that isn't also received via Meshtastic), I would like the option to automatically forward that data to the mesh.

I think it would be most intuitive to be added as another preference alongside the "Enable relay to server". It's the same idea, just reversed data flow.

Use case:

I may have multiple users in the field running ATAK with the Meshtastic Plugin, a single user connected to both the mesh and a local TAK server, and several "HQ" personnel utilizing WinTAK, WebTAK, etc.

As of right now, all of the TAK server users will receive data from the Meshtastic users in the field, but any data added by the TAK server users will have to be manually broadcasted by the one node that is connected to both.

@niccellular
Copy link
Member

No, this will flood your meshtastic network.

@bmswens
Copy link
Author

bmswens commented Jul 30, 2024

Would you consider at least supporting minimal COT events, such as the ones that are already supported via the plugin?
Even just PLI and GeoChat events would help integration immensely.
Making it opt-in just like pushing to the server would also prevent accidental flooding.

@niccellular
Copy link
Member

Takserver doesn't speak the meshtastic protobufs

@niccellular
Copy link
Member

@bmswens See release 1.0.28

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants