You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe:
The uptime is reported as os.uptime() but doesn't give any indication of when homebridge was last restarted. It would be useful to help troubleshoot, for example, if there was a specific module that forced a restart of the homebridge service without necessarily causing a server restart.
Also, just as a point of confusion, initially I thought that Uptime meant Homebridge Uptime, not Server Uptime. It would be still useful to have both values, however.
Describe the solution you'd like:
I'm not sure if it's as simple as modifying os.uptime() here to process.uptime() and importing the process nodeJS module (e.g., /src/modules/status.service.ts. Then, to output this on the appropriate status pages.
There's a better way to refactor the uptime calculation so you wouldn't have to repeat it twice though, but just as an example:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Is your feature request related to a problem? Please describe:
The uptime is reported as
os.uptime()
but doesn't give any indication of when homebridge was last restarted. It would be useful to help troubleshoot, for example, if there was a specific module that forced a restart of the homebridge service without necessarily causing a server restart.Also, just as a point of confusion, initially I thought that
Uptime
meantHomebridge Uptime
, notServer Uptime
. It would be still useful to have both values, however.Describe the solution you'd like:
I'm not sure if it's as simple as modifying
os.uptime()
here toprocess.uptime()
and importing theprocess
nodeJS module (e.g.,/src/modules/status.service.ts
. Then, to output this on the appropriate status pages.There's a better way to refactor the uptime calculation so you wouldn't have to repeat it twice though, but just as an example:
Describe alternatives you've considered:
N/A
Additional context:
N/A
The text was updated successfully, but these errors were encountered: