Auto Update Repeater Telemetry #105

New Issue

2026-10-05T01:57:26+02:00

adam commented

2026-10-05 01:57:26 +02:00

Hi)
If you implemented telemetry history on repeater page by manual updating, why not to add button "subcribe" with period choices( 10,30,60 min) for auto add telemetry history? Would be a great feature for monitoring own repeaters( only for admin role). Thanks for app, use it 24/7 for testing and communication

Hi) If you implemented telemetry history on repeater page by manual updating, why not to add button "subcribe" with period choices( 10,30,60 min) for auto add telemetry history? Would be a great feature for monitoring own repeaters( only for admin role). Thanks for app, use it 24/7 for testing and communication

adam closed this issue

2026-10-05 01:57:26 +02:00

adam commented

2026-10-05 01:57:27 +02:00

Totally get where you're coming from; you're not the first to ask 🙂 repeater telemetry history is a middle ground compromise actually haha. I'm not willing to add a feature that makes it easy for people to generate 100% automated traffic on the mesh via RemoteTerm; it makes it easy for people who don't know what they're at risk of to clog up the mesh with garbage traffic (sorta like what often happens with Meshtastic). So, I'm happy to track the data, and for people who understand the risks, they're free to ping the API to collect that data, but I don't want to make traffic-spew a simple one-click feature for people who don't know what they're doing/don't understand.

I am considering a locked every-two-hours option with a maximum repeater cap to prevent excessive messaging but I haven't settled fully on it yet. It would contravene a value that I think is important (no simple way to generate automated traffic) but I know it's a feature people really care about.

Totally get where you're coming from; you're not the first to ask 🙂 repeater telemetry history is a middle ground compromise actually haha. I'm not willing to add a feature that makes it easy for people to generate 100% automated traffic on the mesh via RemoteTerm; it makes it easy for people who don't know what they're at risk of to clog up the mesh with garbage traffic (sorta like what often happens with Meshtastic). So, I'm happy to track the data, and for people who understand the risks, they're free to ping the API to collect that data, but I don't want to make traffic-spew a simple one-click feature for people who don't know what they're doing/don't understand. I am considering a locked every-two-hours option with a maximum repeater cap to prevent excessive messaging but I haven't settled fully on it yet. It would contravene a value that I think is important (no simple way to generate automated traffic) but I know it's a feature people really care about.

adam commented

2026-10-05 01:57:28 +02:00

Okay I think I've been won over with an every-six-hours check cycle for a maximum of eight nodes. I'll implement later today.

Okay I think I've been won over with an every-six-hours check cycle for a maximum of eight nodes. I'll implement later today.

adam commented

2026-10-05 01:57:29 +02:00

Okay I think I've been won over with an every-six-hours check cycle for a maximum of eight nodes. I'll implement later today.

Okay, thanks) if you care about abuse of mesh network,sooo. Maybe only for direct repeaters?) with 2 hours delay)) I wasn’t familiar with the protocol, but as i think( is it true) direct messages is not going to flood ways all over city mesh

> Okay I think I've been won over with an every-six-hours check cycle for a maximum of eight nodes. I'll implement later today. Okay, thanks) if you care about abuse of mesh network,sooo. Maybe only for direct repeaters?) with 2 hours delay)) I wasn’t familiar with the protocol, but as i think( is it true) direct messages is not going to flood ways all over city mesh

adam changed title from ~~Auto Update Repeater Telemetry~~ to Auto Update Repeater Telemetry

2026-10-27 12:25:11 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#105