-
Notifications
You must be signed in to change notification settings - Fork 991
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
Reply to Repeater in DeviceTelemetry module #2661
Conversation
How will one be able to select the repeater as destination, since it is not in the NodeDB? Also currently upon receiving the response from the repeater, the other nodes will send out their NodeInfo and ask for a response from the repeater (because they don't have it in their NodeDB), but it will not be able to answer. |
That is a good point. I forgot that sending with a --dest tries to pull from NodeDB. I'm not sure how this will behave with a forged request, but I intend to experiment with it in the C# client, if nothing else to satisfy my own curiosity. 😅 Any ideas for an alternative? Almost wondering if we need some sort of heartbeat / status module in the long term. Traceroute lets you know it's still alive, but folks want something to know the repeater isn't about to have a dead battery in solar installations especially. |
The default broadcast of the DeviceTelemetry is actually like a heartbeat/status module, right? I definitely see why getting the battery status is useful and being able to request it seems like a nice approach in order to still have the advantage of a repeater not contributing to traffic load. However, currently the only way to make this possible is when the repeater also has the NodeInfoModule and thus it would be stored in each node’s NodeDB. Actually the only thing you need to know is its NodeNum, but letting users write that down sounds a bit cumbersome 😅 Not sure how this would work client-wise, because it doesn’t know the node that responded. Maybe something like “A repeater with NodeNum x responded with: …“ |
🤖 Pull request artifacts
|
Tested in C# client (WIP) and seems to work Repeater logs: |
No description provided.