Get TimeZoneOffset for remote gateway across gateway network

Ignition
,
1

Working on a central cloud Ignition server that has multiple gateway network systems attached for reporting.

How would I query the TimeZoneOffset for the remote systems across the gateway network, please? A script method is preferred, but it's in the reporting scheme.

2

Each gateway has a [System]Timezone tag. You could create a reference tag in your site tag provider that reads that value and then on the central server you would have access to it assuming they are set up as remote tag providers. Ultimately though everything is in UTC time so you shouldn't really need this

3

XY, why do you think you need this information/what is your actual end goal?

The direct answer to your question could be "add a gateway message handler and run a script that invokes it", but the primary question stands.

4

Trying to get the time zone offsets into reports so that the receiver knows how to interpret the data. Have had issues with server replacements not capturing ignition.conf overrides of timezone setup & similar, so trying to make sure it's robust.

Per Nol's item, I could create a tag in each realtime or history set tag provider in the remote gateway's and pull the System time & Timezone tags in. But I cannot directly query the remote System tag provider that I'm aware of. (Though my ignorance is legion.)

5

If you create a message handler in the remote gateway, you can then use system.util.sendRequest() and have the remote gateway return the offsets directly.

6

Tag method:
siteA:

  • Create a new tag [siteA]Timezone, reference type pointed to [system]Timezone

central:

  • presumably [siteA] is set up as remote tag provider so you can access the timezone as [siteA]Timezone in your reports

Gateway message method:
siteA:

  • Create a message handler that when received it grabs the timezone and then returns the value

central:

  • Create a script that you pass a server name and it fires the gateway message to request the timezone

Message handler is better if you only want it for the report to call the script. Tag I think is better because then your central server could monitor it on a status page if you ever wanted and/or you could enable history or even an alarm on it if not what you expect.

7

Thank you. Guess I'm creating a series of message handler receipts & a send setup.

8

Yeah, I definitely see the need for it. Reports can be ran from anywhere but when you have people in one time zone talking to others in a different time zone and discussing times but the reports show different times based upon where they're run from it could create confusion.