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]: Display LocalStats #1290

Closed
1 task done
GUVWAF opened this issue Oct 5, 2024 · 4 comments · Fixed by #1307
Closed
1 task done

[Feature Request]: Display LocalStats #1290

GUVWAF opened this issue Oct 5, 2024 · 4 comments · Fixed by #1307
Labels
enhancement New feature or request

Comments

@GUVWAF
Copy link
Member

GUVWAF commented Oct 5, 2024

Contact Details

No response

Tell us your idea.

The device now sends its LocalStats over the PhoneAPI every 15 min. It includes statistics like the amount of good and bad packets received, amount of transmitted packets and, more recently (meshtastic/protobufs#591), the amount of duplicate received messages, amount of transmitted relayed packets and canceled relayed packets. As mentioned in #1200, it thus gives some more raw data from the device that's otherwise not available.
It would be nice to show this somewhere in the Android app, maybe on the device connection page (like iOS), but I'm unsure what the best place would be.

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@GUVWAF GUVWAF added the enhancement New feature or request label Oct 5, 2024
@Kealper
Copy link

Kealper commented Oct 10, 2024

I feel like the empty spot below the option to provide phone location to the current device would be a great place for this extra info. It's an empty area that's already available and otherwise unused, so it makes sense to put that sort of local device specific data in there.

@b8b8
Copy link

b8b8 commented Oct 12, 2024

That area is not actually existent if you have many mesh devices on your list since the scrolling makes nodes disappear at the top. But rejigging the list to force a separate area down there could work.
image

@garthvh
Copy link
Member

garthvh commented Oct 12, 2024

The data is designed for widgets, long duration for things like always on screens.

@Kealper
Copy link

Kealper commented Oct 12, 2024

That area is not actually existent if you have many mesh devices on your list since the scrolling makes nodes disappear at the top. But rejigging the list to force a separate area down there could work. image

Clearly, I need to up my game! 🤣

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

Successfully merging a pull request may close this issue.

4 participants