Summary
The Running time value displayed in LarePass for Olares devices (for example Olares One or systems running Olares OS) does not appear to reflect the actual current system uptime.
Instead, it seems to represent the amount of time since the device was first connected or registered with LarePass.
After rebooting or fully power cycling the system, the displayed running time continues increasing rather than resetting to reflect the new uptime.
Current Behavior
Example behavior observed:
- Olares system has been online for ~90+ days according to LarePass
- System is rebooted or completely powered off/on
- After reconnecting, LarePass still shows the same long-running duration instead of resetting
This suggests the value is tracking something closer to:
- Time since initial pairing
- Time since first registration
- Time since LarePass association
rather than:
Expected Behavior
The Running time field should reflect the current live uptime of the Olares system itself.
After:
- Restart
- Shutdown
- Power loss
- Reboot
- OS restart
the uptime value should reset accordingly.
Example:
- System rebooted 15 minutes ago
- LarePass should display approximately
15 minutes
- Not
90+ days
Suggested Improvements
Option A: Use Actual System Uptime
Retrieve and display the true host uptime directly from the Olares OS/device.
For example:
- Kernel uptime
- Host OS uptime
- Device uptime since last boot
This would align the displayed metric with user expectations.
Option B: Differentiate the Metrics
If both values are useful, consider separating them into distinct fields such as:
System UptimeConnected SinceRegistered Since
This would avoid ambiguity while still preserving long-term connection metadata.
Additional Notes
This may simply be a labeling issue where the current metric is technically functioning as intended but is being presented as uptime.
If so, clarifying the distinction in the UI would still improve operational clarity significantly.
Summary
The
Running timevalue displayed in LarePass for Olares devices (for example Olares One or systems running Olares OS) does not appear to reflect the actual current system uptime.Instead, it seems to represent the amount of time since the device was first connected or registered with LarePass.
After rebooting or fully power cycling the system, the displayed running time continues increasing rather than resetting to reflect the new uptime.
Current Behavior
Example behavior observed:
This suggests the value is tracking something closer to:
rather than:
Expected Behavior
The
Running timefield should reflect the current live uptime of the Olares system itself.After:
the uptime value should reset accordingly.
Example:
15 minutes90+ daysSuggested Improvements
Option A: Use Actual System Uptime
Retrieve and display the true host uptime directly from the Olares OS/device.
For example:
This would align the displayed metric with user expectations.
Option B: Differentiate the Metrics
If both values are useful, consider separating them into distinct fields such as:
System UptimeConnected SinceRegistered SinceThis would avoid ambiguity while still preserving long-term connection metadata.
Additional Notes
This may simply be a labeling issue where the current metric is technically functioning as intended but is being presented as uptime.
If so, clarifying the distinction in the UI would still improve operational clarity significantly.