Actions
Feature #2530
openEnsure correct timezone for VDR
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
10/28/2017
Due date:
% Done:
0%
Estimated time:
Description
When a new VDR server is added to VDR manager its timezone seems to default to CET which results in timers being wrong for all other time zones. It is not obvious that this needs changing and has led to several missed recordings. May I request that the timezone be set automatically to that of the server (of possible) or that the user is promoted to set the timezone when a server is added?
This catches me out each time I change Android device and install the app.
Updated by bju almost 7 years ago
I've analyzed the data flow.
Data flow from server to client
- Timer and Epg data contains no localized time format. Instead the number of seconds since 1970 is sent to the client.
- The client creates Date objects using the transmitted value.
- The dates are formatted for displaying using the local timezone of the android system. So all values shown should be in local time.
Data flow from client to server
- The client constructs the timer string using his local time informations and sends this data to the server
- The servers parses the timer string and creates a timer without any conversion. So the clients local time information are resulting in server timer entries with the wrong (unconverted) time.
Solution
- The client converts his timer input into seconds since 1970 based on the local time of the android system.
- The converted time is sent to the server. A special handling is needed for modified recurrent timers based on day(s) of week.
- The server converts the seconds into his own local time and creates the timer.
Actions