Rest API runTimeInfo Timezone
Hello support,
We are trying to use the API endpoint rest/v3/servers/<guid>/runtimeInfo to get a given server's timezone and local time. We are generally able to use the ‘timeZoneId' value in the response to get the IANA timezone and derive what we want from that. This works across many accounts, but for a single account we are getting contradicting values in the API response. For example, one server has 'UTC' as the 'timeZoneId', but the 'timeZoneOffsetMs' value is -14400000 which maps to the EST timezone. Generally however we see the 'timeZoneId' to be America/Detroit when the 'timeZoneOffsetMs’ value is -14400000.
Can you please provide more explanation as to which of the fields to use and why sometimes they are synonymous and sometimes unrelated?
Additionally, we see the 'synchronizedTimeMs' and 'osTimeMs' fields. Can you explain what these fields represent as well?
Thank you,
Elan
-
hello support,
were you able to answer my question above?
Thank you
0 -
Hello support,
Were you able to answer my question above?
Thank you,
Elan
0 -
Hello support,
Were you able to answer my previous question?
Thank you, Elan
0 -
Hi Paul,
Could you give us more detail on this specific case: "one server has 'UTC' as the 'timeZoneId', but the 'timeZoneOffsetMs' value is -14400000, which maps to the EST timezone"?
How do you reproduce it? I've tried a number of servers, both standalone sites and multiple servers merged into a single site, and I haven't been able to see this behaviour.
In general, a report like this is much easier for us to act on if it includes your Media Server version and either a screen recording or step-by-step reproduction steps. That gives us a clear picture of what you're seeing.
At the moment there isn't much I can explain, because your understanding of 'timeZoneId' and 'timeZoneOffsetMs' is correct, and the API documentation describes the same behaviour: https://meta.nxvms.com/doc/developers/api-tool/rest-v4-servers-id-runtimeinfo-get
To move this forward, could you confirm the following?
- Which Media Server version are you running?
- Is the timezone set correctly at the OS level on the affected server?
- When you mention "one account", which account do you mean, and what type of account is it?
- What does the Time Synchronization page show in the UI?
There are a number of unknowns here. Once we have those details, we should be able to identify what to check next and suggest steps you can apply.
Thanks.
0 -
Hello Ichiro,
I understand. Here are the answers to the questions you posed:
The media server version is 6.0.6.41837
The OS Time and VMS Time match and are both 2026-09-14 10:37:36 (UTC -5)
Apologies, when I said account. It really is only on one of the sites inside the user's account.
We don't have access to the desktop application, so I don't see a Time Synchronization page. I don't see a time sync page on the browser.
Thank you,
Elan0 -
Hi Paul,
Thanks for the information.
Since both of us don't have access to the site and haven't been able to reproduce the issue on our end, our current suggestion would be to update the Mediaserver and confirm that the cameras and the server OS are all set to the same timezone (which you may have already done).
A couple of notes on why:
- Updating the Mediaserver ensures the latest code base is in place, so if the issue recurs we're troubleshooting against current code rather than chasing something that may already be fixed.
- If you'd like us to take this further, we'll most likely need access to the site. This isn't a case we've seen before, so there's limited prior art for us to work from.
Thanks for your understanding.
0
Please sign in to leave a comment.
Comments
6 comments