search

tpmullan / OctoPrint-DetailedProgress

28 stars 14 forks source link

ETA display time seems to be ignoring system timezone #41

Open gdeconto opened 3 years ago

gdeconto commented 3 years ago

I noticed that my ETA time shows as 7 hours more than what I manually compute the end time to be based on how many hours/min/etc are left to print.

It seems it may be ignoring the timezone I set; for example, my current (5:55PM) that will take about 1.5 hours more to print is showing 2:31AM finish time tomorrow instead of 7:30PM

AlDaveed commented 3 years ago

I have the same issue, I can't figure what reference time is used for the ETA so I can modify it. My ETA is usually about a day off.

dman97 commented 3 years ago

I have the same issue, is there a way to adjust this?

tnybrt commented 3 years ago

Same thing but I'm unable to find a place to adjust it at

dman97 commented 3 years ago

Same thing but I'm unable to find a place to adjust it at

I found the issue was that I did not have the time zone set in my Raspberry Pi. Once I completed the localization settings the time was correct.

gdeconto commented 3 years ago

Dman97, that was the first thing I checked. The pi time is set correctly

ghod90 commented 3 years ago

Having the same issue

Arsolix commented 2 years ago

have this issue also

wjcarpenter commented 2 years ago

I hope I'm not over-explaining this to folks who already understand this completely.

On Linux, the timezone is controlled by the TZ environment variable. Different users can have different preferences for that variable. If you run OctoPrint as a service or inside a Docker image, it could be that the TZ variable is not set correctly or not set at all. So, even if you see things in the correct timezone when you log onto your server, it can still be wrong for various services and processes that are not started from the command line.

(The sample docker-compose file given on the OctoPrint web site does the right thing for timezeon for the config editor but not for the octoprint process itself. That's how I went down this path.)