What's the impact of the timezone setting configured in the Signagelive Chrome application?

The timezone configured in the Signagelive Chrome app only serves one purpose, which is the timezone that is reported back to the Signagelive cloud as the "Configured Timezone". This can be seen in the System tab and it is also returned in the player details via our API.

It does not, however, have any impact on the time set on the device and therefore does not impact things like media playback, screen control etc. It is purely for reporting only and exists only because there was no built in capabilities to be able to access the date and time / timezone settings at the OS level.

This means that the devices will always adhere to the timezone configuration set in the Google Admin console.

If the timezone set in the Google Admin console is different to the timezone configured in Signagelive then the configured timezone that is visible in the Signagelive UI or returned in the player details via our API will not reflect the actual timezone on the player.

So your player can be in two different scenarios:

1. The Timezone is set via Google Admin but the Signagelive timezone setting has not been changed (two different timezones configured): The Signagelive UI will show the incorrect Timezone in the  player System tab but the player will update its playback and policy and the time will match the timezone set via Google Admin.
2. The Timezone is set via Google Admin and the Signagelive timezone setting has been set to location timezone (same timezone configured): The player will update to the new timezone via a policy sync and the Signagelive UI will reflect the correct Timezone in the player System tab.