Consider emoncms using user account TZ rather than browser TZ when viewing data and dashboards etc

[pb66]

See https://community.openenergymonitor.org/t/timezone-in-emoncms/7569?u=pb66

In short (for example) when we look at a solar plot for any given day it should start to increase AM and tail off PM as a rule. it should not look like the sun rose at 6pm and set again at 6am and peaked at midnight just because it is UK data viewed from Australia. In most cases the data is related to the user account TZ and not the TZ that the data is being viewed from at any given time.

If users in 5 different TZ's view the same data that relates to a single location at the same time, it should appear the same to all users, not be TZ adjusted for each user.

[TrystanLea]

Its a good idea, I think this would be worth implementing

[emrysr]

I've implemented a timezone dropdown in the graph module

emoncms/graph#51

[pb66]

This issue should not be closed as the feature implemented in the graph module only affects the graph module. We need a system wide fix so that ALL data is presented in the user account TZ.

In addition to this it's worth noting that the use of browser time rather than server time also has it's issues, see https://community.openenergymonitor.org/t/emonpi-gone-mental/11206?u=pb66.

The bottom line is it really is irrelevant where in the world the data is being viewed or what time the client device thinks it might be. The sun still comes up at the same time for the house being monitored, the heating still comes on at the same time and when we look at the feed or inputs pages if the last 10s update was less than 10s ago it should display a number less than 10, even if the client device is an hour slow, the last update was still under 10s ago, not an hour and 10s ago.

[camelcamro]

still waiting ? - still no solution ?
i don'T undersstand what is here so complicated that api use the time from installed/configured where the server is running. that is nothing special, isn't it ?