Increase max uptime stats from 49 days to 136 years #1003
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
agessaman
pushed a commit
to agessaman/MeshCore
that referenced
this pull request
Nov 8, 2025
…d-max-uptime Increase max uptime stats from 49 days to 136 years
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR resolves the issue where repeaters and room servers can only show a maximum uptime of ~49 days, before rolling back to zero days uptime. This is a simpler implementation of what #444 was looking to achieve.
This has been tested on RAK4631 as a repeater. I've also manually set the uptime millis to extremely large values, and successfully received 69 days, 2049 days and 49710 days uptime in repeater stats replies.
Users will no longer think their devices have rebooted due to an error.