Battery level for repeaters #69

New Issue

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

adam commented

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

Thanks for building this! It's awesome.

I'd love to keep track of the battery level in my solar repeater using remoteterm. We've already got remote admin capability. Maybe there could be a little battery symbol next to favorited repeaters for which I've saved login info?

Claude suggests this for a formula: https://github.com/meshcore-dev/meshcore-ha/blob/ede8cb6/custom_components/meshcore/utils.py#L137-L147 - (voltage_mv - 3000) / (4200 - 3000) * 100

Thanks for building this! It's *awesome*. I'd love to keep track of the battery level in my solar repeater using remoteterm. We've already got remote admin capability. Maybe there could be a little battery symbol next to favorited repeaters for which I've saved login info? Claude suggests this for a formula: https://github.com/meshcore-dev/meshcore-ha/blob/ede8cb6/custom_components/meshcore/utils.py#L137-L147 - `(voltage_mv - 3000) / (4200 - 3000) * 100`

adam closed this issue

2026-10-05 01:55:58 +02:00

adam commented

2026-10-05 01:55:58 +02:00

So we already surface the voltage for repeaters in the pane once loaded:

We've had a similar request in https://github.com/jkingsman/Remote-Terminal-for-MeshCore/issues/32, and for right now I'm going to stand by that, which is that it's an important design goal for me to not enable any sort of automated traffic emissions from the radio. Traffic sent due to user impulse, or in direct response to another action (e.g. bots) is fine, but I don't want to put RemoteTerm in the position of sending any kind of fully automated traffic on the mesh.

As I mentioned in that thread, it's super easy to have a script for monitoring run for data collection that uses RemoteTerm's APIs to collect data, but I don't want to put any flavor of "background traffic sent without user demand or event response" in the app -- people who use it mindfully are fine, but adding to (or making it trivial to add to) the background traffic for all users gives me fears of lowering the barriers that prevent a MeshTadtic style of noise proliferation.

So, I like the idea, and think it would be a slick feature, but it's not going to be something I implement right now, sorry!

So we already surface the voltage for repeaters in the pane once loaded: ![Screenshot_20260324-064355.png](https://github.com/user-attachments/assets/c2873bb2-7632-48d1-8170-23a1a2ee2675) We've had a similar request in https://github.com/jkingsman/Remote-Terminal-for-MeshCore/issues/32, and for right now I'm going to stand by that, which is that it's an important design goal for me to not enable any sort of automated traffic emissions from the radio. Traffic sent due to user impulse, or in direct response to another action (e.g. bots) is fine, but I don't want to put RemoteTerm in the position of sending any kind of fully automated traffic on the mesh. As I mentioned in that thread, it's super easy to have a script for monitoring run for data collection that uses RemoteTerm's APIs to collect data, but I don't want to put any flavor of "background traffic sent without user demand or event response" in the app -- people who use it mindfully are fine, but adding to (or making it trivial to add to) the background traffic for all users gives me fears of lowering the barriers that prevent a MeshTadtic style of noise proliferation. So, I like the idea, and think it would be a slick feature, but it's not going to be something I implement right now, sorry!

adam commented

2026-10-05 01:55:59 +02:00

Also, sorry for not saying first — thank you so much for your kind words. It means so much to me! Sorry it's a veto on this issue for now, but hopefully it doesn't dampen the usefulness for you ❤️️

Also, sorry for not saying first — thank you so much for your kind words. It means so much to me! Sorry it's a veto on this issue for now, but hopefully it doesn't dampen the usefulness for you ❤️️

adam commented

2026-10-05 01:56:00 +02:00

Hey no problem, and I get it. Seems like a reasonable decision. Still, thanks for making this!

Hey no problem, and I get it. Seems like a reasonable decision. Still, thanks for making this!

adam commented

2026-10-05 01:56:00 +02:00

I got ground down 😜 Opt-in telemetry tracking for up to eight repeaters, polling once every eight hours, is now supported on the main branch. A docker build will come later tonight.

I got ground down 😜 Opt-in telemetry tracking for up to eight repeaters, polling once every eight hours, is now supported on the main branch. A docker build will come later tonight.

adam commented

2026-10-05 01:56:01 +02:00

Hah! Awesome!

Hah! Awesome!

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#69