Get correct time zone from Concerto #45
Comments
The goal is to allow the Player to behave according to the Time Zone assigned in the Concerto admin panel. This should make screen on/off controls more reasonable when the client PC is under bandshell control. Should help with concerto/bandshell#45.
|
It seems like debian wants both /etc/localtime and /etc/timezone to be udpated in order for the new timezone to take hold. We'll probably want to do something like the following whenever a new value is pulled from the server: cp -vf /usr/share/zoneinfo/$tz /etc/localtime
echo $tz | tee /etc/timezone@asquared: will it be possible to make this persistent, or should we just go ahead and reapply the config value at each boot? |
Admins can set the screen's timezone in Concerto, and the latest concerto-hardware plugin will transmit that information to the screen via the API. The on/off times set in concerto-hardware are read as local time to the time zone set in the Screen. The only thing from #45 that this does not resolve is setting the system time. Screen name is also now saved to aid in debugging via the status page.
|
Can anyone think of a reason we need to set the system timezone? If we can think of things outside of Bandshell that need the TZ, we can set it with the above method. Otherwise the ticket can be closed. |
|
It's probably better if the system doesn't just have UTC time, in case the user tries to do other useful things with the computer and finds it has a different time from the application running on it. |
In the field, at least one Concerto Player-based with scheduling problems (being off during the day) was seen to have a Time Zone of UTC, causing the schedule to be offset.
Concerto currently maintains a per-screen
time_zoneon the Screen model. Bandshell should fetch that setting and apply it to the local image in a persistent fashion.The text was updated successfully, but these errors were encountered: